Am 01.09.2008 um 18:17 schrieb Avi Kivity <[EMAIL PROTECTED]>:
Alexander Graf wrote:
We can't change struct kvm_sregs, since the structure size is
encoded in the ioctl number. We need a new struct and new
ioctls. The same was done for mpstate, for example.
Urks - doesn't sounds fast to me.
It's only for save/restore, not in any fast path.
Ah, so we don't sync hflags with the userspace on every transition but
only request it on save/restore?
Sounds good.
There's more info needed, btw. Whether the guest is in guest mode
or host mode; what the current vmcs is; the value of eflags.if at
the time vmrun was executed; and probably more.
Do we really want to support storing the state when within the
Level2 VM? Can't we just #VMEXIT as soon as we switch to userspace
or so? That would probably simplify things a lot.
Great idea. What do we give as the exit reason?
I thought of INTR here. That should be a nop in every VMM. Even if
not, worst case it would end in an hlt that still fires on the next
timer.
Alex
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
