KVM: nSVM: Transparently handle L1 -> L2 NMI re-injection

Browse source

A NMI that L1 wants to inject into its L2 should be directly re-injected,
without causing L0 side effects like engaging NMI blocking for L1.

It's also worth noting that in this case it is L1 responsibility
to track the NMI window status for its L2 guest.

Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
Message-Id: <f894d13501cd48157b3069a4b4c7369575ddb60e.1651440202.git.maciej.szmigiero@oracle.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

...

This commit is contained in:

Maciej S. Szmigiero 2022-05-02 00:07:34 +02:00 • committed by Paolo Bonzini

parent 2d61391270

commit 159fc6fa3b

3 changed files with 20 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

12

arch/x86/kvm/svm/nested.c

View file

7

arch/x86/kvm/svm/svm.c

View file

1

arch/x86/kvm/svm/svm.h

View file