From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, jmattson@google.com,
sean.j.christopherson@intel.com
Subject: [PATCH 0/2] KVM: nSVM: Check reserved values for 'Type' and invalid vectors in EVENTINJ
Date: Sat, 17 Oct 2020 00:02:32 +0000 [thread overview]
Message-ID: <20201017000234.42326-1-krish.sadhukhan@oracle.com> (raw)
According to sections "Canonicalization and Consistency Checks" and "Event
Injection" in APM vol 2,
VMRUN exits with VMEXIT_INVALID error code if either:
- Reserved values of TYPE have been specified, or
- TYPE = 3 (exception) has been specified with a vector that does not
correspond to an exception (this includes vector 2, which is an NMI,
not an exception).
Patch# 1 adds these checks to KVM.
Patch# 2 adds tests for these checks.
[PATCH 1/2] KVM: nSVM: Check reserved values for 'Type' and invalid
[PATCH 2/2] nSVM: Test reserved values for 'Type' and invalid vectors in
arch/x86/include/asm/svm.h | 4 ++++
arch/x86/kvm/svm/nested.c | 14 ++++++++++++++
2 files changed, 18 insertions(+)
Krish Sadhukhan (1):
KVM: nSVM: Check reserved values for 'Type' and invalid vectors in EVENTINJ
x86/svm_tests.c | 40 ++++++++++++++++++++++++++++++++++++++++
1 file changed, 40 insertions(+)
Krish Sadhukhan (1):
nSVM: Test reserved values for 'Type' and invalid vectors in EVENTINJ
next reply other threads:[~2020-10-17 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 0:02 Krish Sadhukhan [this message]
2020-10-17 0:02 ` [PATCH 1/2] KVM: nSVM: Check reserved values for 'Type' and invalid vectors in EVENTINJ Krish Sadhukhan
2020-10-17 0:02 ` [PATCH 2/2] nSVM: Test " Krish Sadhukhan
2020-10-17 6:12 ` Nadav Amit
2020-10-19 17:30 ` Krish Sadhukhan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201017000234.42326-1-krish.sadhukhan@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).