On Sun, Feb 24, 2013, Jan Kiszka wrote about "[PATCH] KVM: nSVM/nVMX: Implement vmexit on INIT assertion":
> From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
>
> On Intel, raising INIT causing an unconditional vmexit. On AMD, this is
> controlled by the interception mask.
Hi,
I never tried to closely follow the KVM code paths related this code,
but I do have one question: The VMX spec says:
"The INIT signal is blocked whenever a logical processor is in VMX root
operation. It is not blocked in VMX non-root operation. Instead, INITs
cause VM exits (see Section 22.3, Other Causes of VM Exits)."
So when running a non-nested L1 guest, or an L2 guest, the new behavior
appears correct. However, it looks like if L1 is running in root
mode (i.e., did VMXON once but not running L2 now), the INIT signal
needs to be blocked, not do what it does now. It appears (but I'm not sure...)
that right now, it causes the L1 guest to lock up, and is not ignored?
Nadav.
--
Nadav Har'El | Monday, Feb 25 2013, 15 Adar 5773
nyh@xxxxxxxxxxxxxxxxxxx |-----------------------------------------
Phone +972-523-790466, ICQ 13349191 |If con is the opposite of pro, is
http://nadav.harel.org.il |congress the opposite of progress?
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
