Kevin P. Lawton wrote:
> If we emulate eflags reads/writes upon traps generated
> on virtualized eflags-related instructions, then the
> values in the real eflags register have nothing to
> do with what the guest thinks. Eflags becomes just
> a register that the guest code never sees.
Well... I don't think that's a good idea.
There are flags, most notably IF, that cannot be
acted upon right away but can also not be stored
in the real flags field. You have to store it
*somewhere*. Virtual flags is the cleanest solution
I can think of.
-- Ramon
