When waking vCPUs in the posted interrupt wakeup handling, do exactly
that and no more. There is no need to kick the vCPU as the wakeup
handler just needs to get the vCPU task running, and if it's in the guest
then it's definitely running.
Signed-off-by: Sean Christopherson <sea...@google.com>
Reviewed-by: Maxim Levitsky <mlevi...@redhat.com>
---
arch/x86/kvm/vmx/posted_intr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/vmx/posted_intr.c b/arch/x86/kvm/vmx/posted_intr.c
index 023a6b9b0fa4..f4169c009400 100644
--- a/arch/x86/kvm/vmx/posted_intr.c
+++ b/arch/x86/kvm/vmx/posted_intr.c
@@ -209,7 +209,7 @@ void pi_wakeup_handler(void)
pi_wakeup_list) {
if (pi_test_on(&vmx->pi_desc))
- kvm_vcpu_kick(&vmx->vcpu);
+ kvm_vcpu_wake_up(&vmx->vcpu);
}
spin_unlock(&per_cpu(wakeup_vcpus_on_cpu_lock, cpu));
}
--
2.34.1.400.ga245620fadb-goog
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
