[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] svm vmexit action sequence

Is there any particular reason why on 32-bits the order is VMLOAD then
HVM_SAVE_ALL_NOSEGREGS, while on 64-bits its is the other way around?
Trying to put in the saving of EAX, I could save a GET_CURRENT() on 32-bits
if I could order things the same way as on 64-bits.

Also, both versions seem to have a redundant GET_CURRENT() right after
the clgi/sti sequence - again, is there a particular reason for this?

Thanks, Jan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.