From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: kvm@vger.kernel.org
Cc: rkrcmar@redhat.com, pbonzini@redhat.com, jmattson@google.com
Subject: [PATCH 0/2 v2]nVMX: Check Host Segment Registers and Descriptor Tables on vmentry of nested guests
Date: Wed, 3 Jul 2019 19:54:34 -0400 [thread overview]
Message-ID: <20190703235437.13429-1-krish.sadhukhan@oracle.com> (raw)
v1 -> v2:
In patch# 2, make_non_canonical() has been made 'inline' to fix a
compilation error.
Patch# 1 implements the following checks, from Intel SDM vol 3C, on
vmentry of nested guests:
- In the selector field for each of CS, SS, DS, ES, FS, GS and TR, the
RPL (bits 1:0) and the TI flag (bit 2) must be 0.
- The selector fields for CS and TR cannot be 0000H.
- The selector field for SS cannot be 0000H if the "host address-space
size" VM-exit control is 0.
- On processors that support Intel 64 architecture, the base-address
fields for FS, GS and TR must contain canonical addresses.
Patch# 2 adds kvm-unit-tests for the above checks.
[PATCH 1/2] KVM nVMX: Check Host Segment Registers and Descriptor Tables on
[PATCH 2/2] kvm-unit-test nVMX: Test Host Segment Registers and Descriptor Tables on
arch/x86/kvm/vmx/nested.c | 26 ++++++++++++++++++++++++--
1 file changed, 24 insertions(+), 2 deletions(-)
Krish Sadhukhan (1):
nVMX: Check Host Segment Registers and Descriptor Tables on vmentry of nested guests
lib/x86/processor.h | 5 ++
x86/vmx_tests.c | 159 ++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 164 insertions(+)
Krish Sadhukhan (1):
nVMX: Test Host Segment Registers and Descriptor Tables on vmentry of nested guests
next reply other threads:[~2019-07-04 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 23:54 Krish Sadhukhan [this message]
2019-07-03 23:54 ` [PATCH 1/2 v2] KVM nVMX: Check Host Segment Registers and Descriptor Tables on vmentry of nested guests Krish Sadhukhan
2019-07-03 23:54 ` [PATCH 2/2 v2]kvm-unit-test: nVMX: Test " Krish Sadhukhan
2019-07-21 18:26 ` Nadav Amit
2019-07-24 15:55 ` Sean Christopherson
2019-07-24 16:12 ` Sean Christopherson
2019-07-25 22:32 ` Krish Sadhukhan
2019-07-25 22:45 ` Jim Mattson
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=20190703235437.13429-1-krish.sadhukhan@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.