From: Xiong Zhang <[email protected]>
Switch PMI handler at KVM context switch boundary because KVM uses a
separate maskable interrupt vector other than the NMI handler for the host
PMU to process its own PMIs. So invoke the perf API that allows
registration of the PMI handler.
Signed-off-by: Xiong Zhang <[email protected]>
Signed-off-by: Mingwei Zhang <[email protected]>
---
arch/x86/kvm/pmu.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/x86/kvm/pmu.c b/arch/x86/kvm/pmu.c
index 9d737f5b96bf..cd559fd74f65 100644
--- a/arch/x86/kvm/pmu.c
+++ b/arch/x86/kvm/pmu.c
@@ -904,11 +904,15 @@ void kvm_pmu_save_pmu_context(struct kvm_vcpu *vcpu)
lockdep_assert_irqs_disabled();
static_call_cond(kvm_x86_pmu_save_pmu_context)(vcpu);
+
+ perf_guest_switch_to_host_pmi_vector();
}
void kvm_pmu_restore_pmu_context(struct kvm_vcpu *vcpu)
{
lockdep_assert_irqs_disabled();
+ perf_guest_switch_to_kvm_pmi_vector(kvm_lapic_get_lvtpc_mask(vcpu));
+
static_call_cond(kvm_x86_pmu_restore_pmu_context)(vcpu);
}
--
2.34.1