| author | Nadav Har'El <nyh@il.ibm.com> | |
| Wed, 25 May 2011 20:11:34 +0000 (23:11 +0300) | ||
| committer | Avi Kivity <avi@redhat.com> | |
| Tue, 12 Jul 2011 08:45:16 +0000 (11:45 +0300) | ||
| commit | 4704d0befb0721274bda863192c4782febb6b94c | |
| tree | f460a211f2307a9ba2db1f641b6907d9572f6cf6 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 99e65e805dea4df061aa4038211112aa96416412 | commit | diff |
KVM: nVMX: Exiting from L2 to L1
This patch implements nested_vmx_vmexit(), called when the nested L2 guest
exits and we want to run its L1 parent and let it handle this exit.
Note that this will not necessarily be called on every L2 exit. L0 may decide
to handle a particular exit on its own, without L1's involvement; In that
case, L0 will handle the exit, and resume running L2, without running L1 and
without calling nested_vmx_vmexit(). The logic for deciding whether to handle
a particular exit in L1 or in L0, i.e., whether to call nested_vmx_vmexit(),
will appear in a separate patch below.
Signed-off-by: Nadav Har'El <nyh@il.ibm.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
This patch implements nested_vmx_vmexit(), called when the nested L2 guest
exits and we want to run its L1 parent and let it handle this exit.
Note that this will not necessarily be called on every L2 exit. L0 may decide
to handle a particular exit on its own, without L1's involvement; In that
case, L0 will handle the exit, and resume running L2, without running L1 and
without calling nested_vmx_vmexit(). The logic for deciding whether to handle
a particular exit in L1 or in L0, i.e., whether to call nested_vmx_vmexit(),
will appear in a separate patch below.
Signed-off-by: Nadav Har'El <nyh@il.ibm.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
| arch/x86/include/asm/vmx.h | diff | blob | history | |
| arch/x86/kvm/vmx.c | diff | blob | history |