On 09/12/2010 09:51 PM, Nadav Har'El wrote:
There are two cases where VM_ENTRY_INTR_INFO_FIELD can potentially not
be cleared by hardware:
...
If neither of these are valid, the code can be removed. If only the
second, we might make it conditional.
Again, unless I'm misunderstanding what you mean, the hardware only
modified vmcs02 (the hardware vmcs), not vmcs12. We need to modify vmcs12
as well, to remove the "valid" bit. If we don't, when L1 enters into the same
L2 again, the same old value will be copied again from vmcs12 to vmcs02,
and cause an injection of the same interrupt again.
Yes, vmcs12 still needs to be updated. So the code cannot be removed,
just the vm
--
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
