diff options
| author | Sean Christopherson <seanjc@google.com> | 2022-05-02 00:07:28 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2022-06-08 04:46:48 -0400 |
| commit | 3741aec4c38fa4123ab08ae552f05366d4fd05d8 (patch) | |
| tree | 4c05473b5fc2ed3f3fb5576cf7814d61ee2b2156 /arch/x86/kvm/svm/nested.c | |
| parent | cd9e6da8048c5b40315ee2d929b6230ce1252c3c (diff) | |
| download | linux-3741aec4c38fa4123ab08ae552f05366d4fd05d8.tar.gz linux-3741aec4c38fa4123ab08ae552f05366d4fd05d8.tar.bz2 linux-3741aec4c38fa4123ab08ae552f05366d4fd05d8.zip | |
KVM: SVM: Stuff next_rip on emulated INT3 injection if NRIPS is supported
If NRIPS is supported in hardware but disabled in KVM, set next_rip to
the next RIP when advancing RIP as part of emulating INT3 injection.
There is no flag to tell the CPU that KVM isn't using next_rip, and so
leaving next_rip is left as is will result in the CPU pushing garbage
onto the stack when vectoring the injected event.
Reviewed-by: Maxim Levitsky <mlevitsk@redhat.com>
Fixes: 66b7138f9136 ("KVM: SVM: Emulate nRIP feature when reinjecting INT3")
Signed-off-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
Message-Id: <cd328309a3b88604daa2359ad56f36cb565ce2d4.1651440202.git.maciej.szmigiero@oracle.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86/kvm/svm/nested.c')
0 files changed, 0 insertions, 0 deletions