From: Euan Harris <euan.harris@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: andrew.cooper3@citrix.com, kevin.tian@intel.com,
jun.nakajima@intel.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] nested vmx: Intercept guest rdmsr for MSR_IA32_VMX_VMFUNC
Date: Tue, 7 Jun 2016 11:53:44 +0100 [thread overview]
Message-ID: <20160607105344.GA21058@citrix.com> (raw)
In-Reply-To: <5756BF9002000078000F2865@prv-mh.provo.novell.com>
On Tue, Jun 07, 2016 at 04:35:28AM -0600, Jan Beulich wrote:
> > @@ -2624,7 +2624,7 @@ static int vmx_msr_read_intercept(unsigned int msr, uint64_t *msr_content)
> > __vmread(GUEST_IA32_DEBUGCTL, msr_content);
> > break;
> > case IA32_FEATURE_CONTROL_MSR:
> > - case MSR_IA32_VMX_BASIC...MSR_IA32_VMX_TRUE_ENTRY_CTLS:
> > + case MSR_IA32_VMX_BASIC...MSR_IA32_VMX_VMFUNC:
> > if ( !nvmx_msr_read_intercept(msr, msr_content) )
> > goto gp_fault;
> > break;
>
> ... retaining this code structure makes it likely that some future
> addition will lead to the same problem again.
The safest solution would be to whitelist the MSRs which Xen handles and
which the guest should be allowed to see, rather than blacklisting which
is essentially what is happening now. That would involve a substantial
change in the code, but aside from that is there any fundamental reason
why it would be a bad idea?
Thanks,
Euan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-07 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 10:18 [PATCH] nested vmx: Intercept guest rdmsr for MSR_IA32_VMX_VMFUNC Euan Harris
2016-06-07 10:35 ` Jan Beulich
2016-06-07 10:53 ` Euan Harris [this message]
2016-06-07 11:39 ` Andrew Cooper
2016-06-08 6:09 ` Tian, Kevin
2016-06-08 11:54 ` Wei Liu
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=20160607105344.GA21058@citrix.com \
--to=euan.harris@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.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).