From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Kevin Tian <kevin.tian@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Jan Beulich <JBeulich@suse.com>
Subject: [PATCH 3/6] x86/vmx: Introduce and use struct vmx_msr_bitmap
Date: Wed, 19 Jul 2017 12:57:54 +0100 [thread overview]
Message-ID: <1500465477-23793-4-git-send-email-andrew.cooper3@citrix.com> (raw)
In-Reply-To: <1500465477-23793-1-git-send-email-andrew.cooper3@citrix.com>
This avoids opencoding the bitmap bases in accessor functions. Introduce a
build_assertions() function to check the structure layout against the manual
definiton. In addition, drop some stale comments and ASSERT() that callers
pass an in-range MSR.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: Jan Beulich <JBeulich@suse.com>
CC: Jun Nakajima <jun.nakajima@intel.com>
CC: Kevin Tian <kevin.tian@intel.com>
Slightly RFC: I think these asserts would probably be better if they were (my
planned but not yet implemented) VM_BUG_ON() which would allow us to print out
a rather more useful error and crash the VM rather than bringing the host
down.
---
xen/arch/x86/hvm/vmx/vmcs.c | 57 ++++++++++++++++++--------------------
xen/include/asm-x86/hvm/vmx/vmcs.h | 10 ++++++-
2 files changed, 36 insertions(+), 31 deletions(-)
diff --git a/xen/arch/x86/hvm/vmx/vmcs.c b/xen/arch/x86/hvm/vmx/vmcs.c
index e36a908..0e1a142 100644
--- a/xen/arch/x86/hvm/vmx/vmcs.c
+++ b/xen/arch/x86/hvm/vmx/vmcs.c
@@ -805,7 +805,7 @@ static void vmx_set_host_env(struct vcpu *v)
void vmx_clear_msr_intercept(struct vcpu *v, unsigned int msr,
enum vmx_msr_intercept_type type)
{
- unsigned long *msr_bitmap = v->arch.hvm_vmx.msr_bitmap;
+ struct vmx_msr_bitmap *msr_bitmap = v->arch.hvm_vmx.msr_bitmap;
struct domain *d = v->domain;
/* VMX MSR bitmap supported? */
@@ -815,68 +815,51 @@ void vmx_clear_msr_intercept(struct vcpu *v, unsigned int msr,
if ( unlikely(monitored_msr(d, msr)) )
return;
- /*
- * See Intel PRM Vol. 3, 20.6.9 (MSR-Bitmap Address). Early manuals
- * have the write-low and read-high bitmap offsets the wrong way round.
- * We can control MSRs 0x00000000-0x00001fff and 0xc0000000-0xc0001fff.
- */
if ( msr <= 0x1fff )
{
if ( type & VMX_MSR_R )
- clear_bit(msr, msr_bitmap + 0x000/BYTES_PER_LONG); /* read-low */
+ clear_bit(msr, msr_bitmap->read_low);
if ( type & VMX_MSR_W )
- clear_bit(msr, msr_bitmap + 0x800/BYTES_PER_LONG); /* write-low */
+ clear_bit(msr, msr_bitmap->write_low);
}
else if ( (msr >= 0xc0000000) && (msr <= 0xc0001fff) )
{
msr &= 0x1fff;
if ( type & VMX_MSR_R )
- clear_bit(msr, msr_bitmap + 0x400/BYTES_PER_LONG); /* read-high */
+ clear_bit(msr, msr_bitmap->read_high);
if ( type & VMX_MSR_W )
- clear_bit(msr, msr_bitmap + 0xc00/BYTES_PER_LONG); /* write-high */
+ clear_bit(msr, msr_bitmap->write_high);
}
else
- HVM_DBG_LOG(DBG_LEVEL_MSR,
- "msr %x is out of the control range"
- "0x00000000-0x00001fff and 0xc0000000-0xc0001fff"
- "RDMSR or WRMSR will cause a VM exit", msr);
-
+ ASSERT(!"MSR out of range for interception\n");
}
void vmx_set_msr_intercept(struct vcpu *v, unsigned int msr,
enum vmx_msr_intercept_type type)
{
- unsigned long *msr_bitmap = v->arch.hvm_vmx.msr_bitmap;
+ struct vmx_msr_bitmap *msr_bitmap = v->arch.hvm_vmx.msr_bitmap;
/* VMX MSR bitmap supported? */
if ( msr_bitmap == NULL )
return;
- /*
- * See Intel PRM Vol. 3, 20.6.9 (MSR-Bitmap Address). Early manuals
- * have the write-low and read-high bitmap offsets the wrong way round.
- * We can control MSRs 0x00000000-0x00001fff and 0xc0000000-0xc0001fff.
- */
if ( msr <= 0x1fff )
{
if ( type & VMX_MSR_R )
- set_bit(msr, msr_bitmap + 0x000/BYTES_PER_LONG); /* read-low */
+ set_bit(msr, msr_bitmap->read_low);
if ( type & VMX_MSR_W )
- set_bit(msr, msr_bitmap + 0x800/BYTES_PER_LONG); /* write-low */
+ set_bit(msr, msr_bitmap->write_low);
}
else if ( (msr >= 0xc0000000) && (msr <= 0xc0001fff) )
{
msr &= 0x1fff;
if ( type & VMX_MSR_R )
- set_bit(msr, msr_bitmap + 0x400/BYTES_PER_LONG); /* read-high */
+ set_bit(msr, msr_bitmap->read_high);
if ( type & VMX_MSR_W )
- set_bit(msr, msr_bitmap + 0xc00/BYTES_PER_LONG); /* write-high */
+ set_bit(msr, msr_bitmap->write_high);
}
else
- HVM_DBG_LOG(DBG_LEVEL_MSR,
- "msr %x is out of the control range"
- "0x00000000-0x00001fff and 0xc0000000-0xc0001fff"
- "RDMSR or WRMSR will cause a VM exit", msr);
+ ASSERT(!"MSR out of range for interception\n");
}
/*
@@ -1094,7 +1077,7 @@ static int construct_vmcs(struct vcpu *v)
/* MSR access bitmap. */
if ( cpu_has_vmx_msr_bitmap )
{
- unsigned long *msr_bitmap = alloc_xenheap_page();
+ struct vmx_msr_bitmap *msr_bitmap = alloc_xenheap_page();
if ( msr_bitmap == NULL )
{
@@ -1958,6 +1941,20 @@ void __init setup_vmcs_dump(void)
register_keyhandler('v', vmcs_dump, "dump VT-x VMCSs", 1);
}
+static void __init __maybe_unused build_assertions(void)
+{
+ struct vmx_msr_bitmap bitmap;
+
+ BUILD_BUG_ON(sizeof(bitmap) != PAGE_SIZE);
+ BUILD_BUG_ON(sizeof(bitmap.read_low) != 1024);
+ BUILD_BUG_ON(sizeof(bitmap.read_high) != 1024);
+ BUILD_BUG_ON(sizeof(bitmap.write_low) != 1024);
+ BUILD_BUG_ON(sizeof(bitmap.write_high) != 1024);
+ BUILD_BUG_ON(offsetof(struct vmx_msr_bitmap, read_low) != 0);
+ BUILD_BUG_ON(offsetof(struct vmx_msr_bitmap, read_high) != 1024);
+ BUILD_BUG_ON(offsetof(struct vmx_msr_bitmap, write_low) != 2048);
+ BUILD_BUG_ON(offsetof(struct vmx_msr_bitmap, write_high) != 3072);
+}
/*
* Local variables:
diff --git a/xen/include/asm-x86/hvm/vmx/vmcs.h b/xen/include/asm-x86/hvm/vmx/vmcs.h
index e318dc2..926e792 100644
--- a/xen/include/asm-x86/hvm/vmx/vmcs.h
+++ b/xen/include/asm-x86/hvm/vmx/vmcs.h
@@ -64,6 +64,14 @@ struct vmx_domain {
unsigned int status;
};
+/* Layout of the MSR bitmap, as interpreted by hardware. */
+struct vmx_msr_bitmap {
+ unsigned long read_low [0x2000 / BITS_PER_LONG];
+ unsigned long read_high [0x2000 / BITS_PER_LONG];
+ unsigned long write_low [0x2000 / BITS_PER_LONG];
+ unsigned long write_high[0x2000 / BITS_PER_LONG];
+};
+
struct pi_desc {
DECLARE_BITMAP(pir, NR_VECTORS);
union {
@@ -116,7 +124,7 @@ struct arch_vmx_struct {
uint64_t cstar;
uint64_t sfmask;
- unsigned long *msr_bitmap;
+ struct vmx_msr_bitmap *msr_bitmap;
unsigned int msr_count;
struct vmx_msr_entry *msr_area;
unsigned int host_msr_count;
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-19 11:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 11:57 [PATCH 0/6] x86/vvmx: Fixes to MSR_BITMAP interception handling Andrew Cooper
2017-07-19 11:57 ` [PATCH 1/6] x86/vmx: Improvements to vmx_{dis, en}able_intercept_for_msr() Andrew Cooper
2017-07-27 5:43 ` Tian, Kevin
2017-07-19 11:57 ` [PATCH 2/6] x86/vpmu: Use vmx_{clear, set}_msr_intercept() rather than opencoding them Andrew Cooper
2017-07-19 12:17 ` Andrew Cooper
2017-07-27 5:46 ` Tian, Kevin
2017-07-19 13:33 ` Boris Ostrovsky
2017-07-19 11:57 ` Andrew Cooper [this message]
2017-07-27 6:02 ` [PATCH 3/6] x86/vmx: Introduce and use struct vmx_msr_bitmap Tian, Kevin
2017-07-27 8:30 ` Andrew Cooper
2017-07-27 9:01 ` Tian, Kevin
2017-07-19 11:57 ` [PATCH 4/6] x86/vvmx: Switch nested MSR intercept handling to " Andrew Cooper
2017-07-27 6:09 ` Tian, Kevin
2017-07-19 11:57 ` [PATCH 5/6] x86/vvmx: Fix handing of the MSR_BITMAP field with VMCS shadowing Andrew Cooper
2017-07-26 8:50 ` Sergey Dyasli
2017-07-27 6:11 ` Tian, Kevin
2017-07-19 11:57 ` [PATCH 6/6] x86/vvmx: Fix auditing of MSR_BITMAP parameter Andrew Cooper
2017-07-27 6:13 ` Tian, Kevin
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=1500465477-23793-4-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xen.org \
/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).