summaryrefslogtreecommitdiff
path: root/lib/memory-notifier-error-inject.c
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-01-10 04:27:05 +0300
committerSean Christopherson <seanjc@google.com>2024-02-23 03:22:41 +0300
commit0ec3d6d1f169baa7fc512ae4b78d17e7c94b7763 (patch)
tree8cff49e9a62a17b432796a0cd404beb4218b2490 /lib/memory-notifier-error-inject.c
parent7b3d1bbf8d68d76fb21210932a5e8ed8ea80dbcc (diff)
downloadlinux-0ec3d6d1f169baa7fc512ae4b78d17e7c94b7763.tar.xz
KVM: x86: Fully defer to vendor code to decide how to force immediate exit
Now that vmx->req_immediate_exit is used only in the scope of vmx_vcpu_run(), use force_immediate_exit to detect that KVM should usurp the VMX preemption to force a VM-Exit and let vendor code fully handle forcing a VM-Exit. Opportunsitically drop __kvm_request_immediate_exit() and just have vendor code call smp_send_reschedule() directly. SVM already does this when injecting an event while also trying to single-step an IRET, i.e. it's not exactly secret knowledge that KVM uses a reschedule IPI to force an exit. Link: https://lore.kernel.org/r/20240110012705.506918-7-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions