[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE
From: |
Sergey Fedorov |
Subject: |
[Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE |
Date: |
Thu, 22 Oct 2015 21:28:58 +0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
Hi all,
I am trying to understand what the difference should be between
DISAS_JUMP and DISAS_UPDATE. Actually, these macros have comments in
include/exec/exec-all.h which say that DISAS_JUMP should be used when
only PC was modified dynamically whereas DISAS_UPDATE should be used
when some other CPU state was (in addition to PC?) modified dynamically.
In fact, every target except ARM AArch64 does not distinguish between
them. As I can see ARM AArch64 seems to suppose that: (1) PC was not
modified when DISAS_UPDATE is used and should be updated with dc->pc
when finishing translation; (2) DISAS_JUMP can be used to indicate that
a new PC value was set and it should be preserved when finishing
translation.
So I'm a bit confused... What the difference should be? Maybe something
should be fixed/clarified to make the comments and the code consistent.
Best regards,
Sergey
- [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE,
Sergey Fedorov <=
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Richard Henderson, 2015/10/22
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Peter Maydell, 2015/10/22
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Sergey Fedorov, 2015/10/23
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Peter Maydell, 2015/10/23
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Sergey Fedorov, 2015/10/23
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Peter Maydell, 2015/10/23
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Sergey Fedorov, 2015/10/23
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Peter Maydell, 2015/10/23
- Re: [Qemu-devel] exec: About DISAS_JUMP and DISAS_UPDATE, Sergey Fedorov, 2015/10/27