Alexander Graf wrote:
It's not visible in the patches I sent, but I did use the hflags for
a VMLOAD+VMRUN+VMSAVE aggregation hack. It's still somewhat flacky
wrt save/restore though, so I didn't send it. Hflags might be useful
nevertheless though.
You mean code patching?
Yes.
That's always fun.
How exactly would you like to see the userspace bridge implemented? I
thought it might be good to put hflags in the x86 arch struct and just
have it transferred in get_sregs and set_sregs. I don't know if I
break any old userspace doing that though...
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.
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.
--
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
