summaryrefslogtreecommitdiffstats
path: root/arch/x86/kvm/svm/svm.c
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2024-01-09 17:27:04 -0800
committerSean Christopherson <seanjc@google.com>2024-02-22 16:22:37 -0800
commit7b3d1bbf8d68d76fb21210932a5e8ed8ea80dbcc (patch)
tree8d6edba5aabbd6550502e80782d86938ba6f7236 /arch/x86/kvm/svm/svm.c
parentbf1a49436ea37b98dd2f37c57608951d0e28eecc (diff)
downloadlinux-stable-7b3d1bbf8d68d76fb21210932a5e8ed8ea80dbcc.tar.gz
linux-stable-7b3d1bbf8d68d76fb21210932a5e8ed8ea80dbcc.tar.bz2
linux-stable-7b3d1bbf8d68d76fb21210932a5e8ed8ea80dbcc.zip
KVM: VMX: Handle KVM-induced preemption timer exits in fastpath for L2
Eat VMX treemption timer exits in the fastpath regardless of whether L1 or L2 is active. The VM-Exit is 100% KVM-induced, i.e. there is nothing directly related to the exit that KVM needs to do on behalf of the guest, thus there is no reason to wait until the slow path to do nothing. Opportunistically add comments explaining why preemption timer exits for emulating the guest's APIC timer need to go down the slow path. Link: https://lore.kernel.org/r/20240110012705.506918-6-seanjc@google.com Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'arch/x86/kvm/svm/svm.c')
0 files changed, 0 insertions, 0 deletions