diff options
| author | Sean Christopherson <seanjc@google.com> | 2023-02-27 11:40:12 +0300 |
|---|---|---|
| committer | Sean Christopherson <seanjc@google.com> | 2023-03-22 22:34:34 +0300 |
| commit | ab2ee212a57bf136b896a47ce37da38a1fdbdc36 (patch) | |
| tree | 6ad64b7860b6d8cc8b81047ebbc19dc0773a39d3 /tools/perf/scripts/python | |
| parent | 400fee8c9b2df61721de8103a4054247bea79fd0 (diff) | |
| download | linux-ab2ee212a57bf136b896a47ce37da38a1fdbdc36.tar.xz | |
KVM: x86: Save/restore all NMIs when multiple NMIs are pending
Save all pending NMIs in KVM_GET_VCPU_EVENTS, and queue KVM_REQ_NMI if one
or more NMIs are pending after KVM_SET_VCPU_EVENTS in order to re-evaluate
pending NMIs with respect to NMI blocking.
KVM allows multiple NMIs to be pending in order to faithfully emulate bare
metal handling of simultaneous NMIs (on bare metal, truly simultaneous
NMIs are impossible, i.e. one will always arrive first and be consumed).
Support for simultaneous NMIs botched the save/restore though. KVM only
saves one pending NMI, but allows userspace to restore 255 pending NMIs
as kvm_vcpu_events.nmi.pending is a u8, and KVM's internal state is stored
in an unsigned int.
Fixes: 7460fb4a3400 ("KVM: Fix simultaneous NMIs")
Signed-off-by: Santosh Shukla <Santosh.Shukla@amd.com>
Link: https://lore.kernel.org/r/20230227084016.3368-8-santosh.shukla@amd.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions