On 3/10/2017 4:36 PM, Paolo Bonzini wrote:
On 10/03/2017 09:02, Yu Zhang wrote:
Hi, you get the scenario where a vmexit is triggered by the hypervisorBesides, is this all the test for UMIP unit test? I.e. do we need toHi Paolo, any suggestions?
construct a scenario in the test to trigger vm exit and let hypervisor
inject a GP fault? - I did not see this scenario in this patch. Or any
other suggestions? :-)
Sorry for the disturb. :)
if you run the unit test on a machine that lacks UMIP support.
We can also add a module parameter to force emulation, so that it will
be possible to test UMIP emulation on newer processors too.
Thanks for your reply, Paolo. :-)
Well, my previous understanding is that there might be a situation on a machine with UMIP
1> when an APP in VM runs instructions such as sgdt addrA,
2> and the addrA may cause anVM exit(e.g. ept violation),
3> next, the emulator in hypervisor need to inject a GP fault to the VM.
Is this situation possible?
This is the case I'd like to test, yet do not know to construct the scenario.
But as to the scenario you described, I do not quit understand.
I mean, on a host which do not support UMIP, although hypervisor may intercept cpuid and
provide an emulated cr4 to guest, how does it guarantee those instructions in VM will cause
a VM exit?