summaryrefslogtreecommitdiff
path: root/virt
diff options
context:
space:
mode:
authorSean Christopherson <seanjc@google.com>2021-11-11 05:07:32 +0300
committerPeter Zijlstra <peterz@infradead.org>2021-11-17 16:49:09 +0300
commitdb215756ae5970aec8ad50257d2eb1678b552b91 (patch)
treefd3340ba891fadd2b567a4f70b32b1355af29f44 /virt
parent73cd107b9685c5308e864061772e4a78a629e4a0 (diff)
downloadlinux-db215756ae5970aec8ad50257d2eb1678b552b91.tar.xz
KVM: x86: More precisely identify NMI from guest when handling PMI
Differentiate between IRQ and NMI for KVM's PMC overflow callback, which was originally invoked in response to an NMI that arrived while the guest was running, but was inadvertantly changed to fire on IRQs as well when support for perf without PMU/NMI was added to KVM. In practice, this should be a nop as the PMC overflow callback shouldn't be reached, but it's a cheap and easy fix that also better documents the situation. Note, this also doesn't completely prevent false positives if perf somehow ends up calling into KVM, e.g. an NMI can arrive in host after KVM sets its flag. Fixes: dd60d217062f ("KVM: x86: Fix perf timer mode IP reporting") Signed-off-by: Sean Christopherson <seanjc@google.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Link: https://lore.kernel.org/r/20211111020738.2512932-12-seanjc@google.com
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions