aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorSean Christopherson <[email protected]>2023-08-25 01:45:32 +0000
committerSean Christopherson <[email protected]>2023-08-29 03:07:43 +0000
commit50011c2a245792993f2756e5b5b571512bfa409e (patch)
tree6b9540c61376a86201e97e9b32e8103c48b510c1 /tools/perf/scripts/python/flamegraph.py
parentKVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS_ADDR not being set (diff)
downloadkernel-50011c2a245792993f2756e5b5b571512bfa409e.tar.gz
kernel-50011c2a245792993f2756e5b5b571512bfa409e.zip
KVM: VMX: Refresh available regs and IDT vectoring info before NMI handling
Reset the mask of available "registers" and refresh the IDT vectoring info snapshot in vmx_vcpu_enter_exit(), before KVM potentially handles a an NMI VM-Exit. One of the "registers" that KVM VMX lazily loads is the vmcs.VM_EXIT_INTR_INFO field, which is holds the vector+type on "exception or NMI" VM-Exits, i.e. is needed to identify NMIs. Clearing the available registers bitmask after handling NMIs results in KVM querying info from the last VM-Exit that read vmcs.VM_EXIT_INTR_INFO, and leads to both missed NMIs and spurious NMIs in the host. Opportunistically grab vmcs.IDT_VECTORING_INFO_FIELD early in the VM-Exit path too, e.g. to guard against similar consumption of stale data. The field is read on every "normal" VM-Exit, and there's no point in delaying the inevitable. Reported-by: Like Xu <[email protected]> Fixes: 11df586d774f ("KVM: VMX: Handle NMI VM-Exits in noinstr region") Cc: [email protected] Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Sean Christopherson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions