KVM: nVMX: Always handle #VEs in L0 (never forward #VEs from L2 to L1)

Always handle #VEs, e.g. due to prove EPT Violation #VE failures, in L0,
as KVM does not expose any #VE capabilities to L1, i.e. any and all #VEs
are KVM's responsibility.

Fixes: 8131cf5b4fd8 ("KVM: VMX: Introduce test mode related to EPT violation VE")
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-ID: <20240518000430.1118488-4-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
index 6798fadaa335025e6848be9d37664bf195264071..643935a0f70ab77b8de56e1c0a145211af5af2ed 100644 (file)
--- a/arch/x86/kvm/vmx/nested.c
+++ b/arch/x86/kvm/vmx/nested.c
@@ -6233,6 +6233,8 @@ static bool nested_vmx_l0_wants_exit(struct kvm_vcpu *vcpu,
                else if (is_alignment_check(intr_info) &&
                         !vmx_guest_inject_ac(vcpu))
                        return true;
+               else if (is_ve_fault(intr_info))
+                       return true;
                return false;
        case EXIT_REASON_EXTERNAL_INTERRUPT:
                return true;