summaryrefslogtreecommitdiff
path: root/virt
diff options
context:
space:
mode:
authorYanfei Xu <yanfei.xu@intel.com>2022-05-23 22:08:21 +0800
committerPaolo Bonzini <pbonzini@redhat.com>2022-05-25 05:18:27 -0400
commitffd1925a596ce68bed7d81c61cb64bc35f788a9d (patch)
treebd58ed1a829eec226ffcb569e943fe448e453086 /virt
parent366d4a12cdcf3d83c8162ff6e0046c123567c754 (diff)
downloadlwn-ffd1925a596ce68bed7d81c61cb64bc35f788a9d.tar.gz
lwn-ffd1925a596ce68bed7d81c61cb64bc35f788a9d.zip
KVM: x86: Fix the intel_pt PMI handling wrongly considered from guest
When kernel handles the vm-exit caused by external interrupts and NMI, it always sets kvm_intr_type to tell if it's dealing an IRQ or NMI. For the PMI scenario, it could be IRQ or NMI. However, intel_pt PMIs are only generated for HARDWARE perf events, and HARDWARE events are always configured to generate NMIs. Use kvm_handling_nmi_from_guest() to precisely identify if the intel_pt PMI came from the guest; this avoids false positives if an intel_pt PMI/NMI arrives while the host is handling an unrelated IRQ VM-Exit. Fixes: db215756ae59 ("KVM: x86: More precisely identify NMI from guest when handling PMI") Signed-off-by: Yanfei Xu <yanfei.xu@intel.com> Message-Id: <20220523140821.1345605-1-yanfei.xu@intel.com> Cc: stable@vger.kernel.org Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions