diff options
| author | Sean Christopherson <[email protected]> | 2024-01-10 01:27:05 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2024-02-23 00:22:41 +0000 |
| commit | 0ec3d6d1f169baa7fc512ae4b78d17e7c94b7763 (patch) | |
| tree | 8cff49e9a62a17b432796a0cd404beb4218b2490 /drivers/usb/cdns3/cdns3-trace.c | |
| parent | KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2 (diff) | |
| download | kernel-0ec3d6d1f169baa7fc512ae4b78d17e7c94b7763.tar.gz kernel-0ec3d6d1f169baa7fc512ae4b78d17e7c94b7763.zip | |
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/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'drivers/usb/cdns3/cdns3-trace.c')
0 files changed, 0 insertions, 0 deletions
