summaryrefslogtreecommitdiffstats
path: root/arch/x86/kvm/vmx/vmx.c
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-05-18 02:04:28 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2024-05-23 18:27:17 +0200
commit40e8a6901a2c983e3e541a363865e02cf591d458 (patch)
treeeea7aa3318a0abaa39be6b802b44329bbc0c6ed4 /arch/x86/kvm/vmx/vmx.c
parentKVM: x86/mmu: Use SHADOW_NONPRESENT_VALUE for atomic zap in TDP MMU (diff)
downloadlinux-40e8a6901a2c983e3e541a363865e02cf591d458.tar.xz
linux-40e8a6901a2c983e3e541a363865e02cf591d458.zip
KVM: VMX: Don't kill the VM on an unexpected #VE
Don't terminate the VM on an unexpected #VE, as it's extremely unlikely the #VE is fatal to the guest, and even less likely that it presents a danger to the host. Simply resume the guest on "failure", as the #VE info page's BUSY field will prevent converting any more EPT Violations to #VEs for the vCPU (at least, that's what the BUSY field is supposed to do). Signed-off-by: Sean Christopherson <seanjc@google.com> Message-ID: <20240518000430.1118488-8-seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to '')
-rw-r--r--arch/x86/kvm/vmx/vmx.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
index 51b2cd13250a..069fbbc1e04a 100644
--- a/arch/x86/kvm/vmx/vmx.c
+++ b/arch/x86/kvm/vmx/vmx.c
@@ -5217,8 +5217,8 @@ static int handle_exception_nmi(struct kvm_vcpu *vcpu)
if (is_invalid_opcode(intr_info))
return handle_ud(vcpu);
- if (KVM_BUG_ON(is_ve_fault(intr_info), vcpu->kvm))
- return -EIO;
+ if (WARN_ON_ONCE(is_ve_fault(intr_info)))
+ return 1;
error_code = 0;
if (intr_info & INTR_INFO_DELIVER_CODE_MASK)