From: David Woodhouse <dwmw2@infradead.org>
To: KarimAllah Ahmed <karahmed@amazon.com>,
Liran Alon <liran.alon@oracle.com>
Cc: konrad.wilk@oracle.com, luto@kernel.org, tglx@linutronix.de,
torvalds@linux-foundation.org, gregkh@linuxfoundation.org,
asit.k.mallick@intel.com, dave.hansen@intel.com,
karahmed@amazon.de, jun.nakajima@intel.com,
dan.j.williams@intel.com, ashok.raj@intel.com,
daniel.kiper@oracle.com, arjan.van.de.ven@intel.com,
tim.c.chen@linux.intel.com, pbonzini@redhat.com,
linux-kernel@vger.kernel.org, ak@linux.intel.com,
kvm@vger.kernel.org, aarcange@redhat.com
Subject: Re: [PATCH] x86: vmx: Allow direct access to MSR_IA32_SPEC_CTRL
Date: Mon, 29 Jan 2018 10:37:44 +0000 [thread overview]
Message-ID: <1517222264.6624.131.camel@infradead.org> (raw)
In-Reply-To: <8bed4a5a-afc6-1569-d9bf-a3e1103e92f8@amazon.com>
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
On Mon, 2018-01-29 at 10:43 +0100, KarimAllah Ahmed wrote:
> On 01/29/2018 09:46 AM, David Woodhouse wrote:
> > Reading the code and comparing with the SDM, I can't see where we're
> > ever setting VM_EXIT_MSR_STORE_{ADDR,COUNT} except in the nested
> > case...
> Hmmm ... you are probably right! I think all users of this interface
> always trap + update save area and never passthrough the MSR. That is
> why only LOAD is needed *so far*.
>
> Okay, let me sort this out in v3 then.
I'm starting to think a variant of Ashok's patch might actually be the
simpler approach, and not "premature optimisation". Especially if we
need to support the !cpu_has_vmx_msr_bitmaps() case?
Start with vmx->spec_ctrl set to zero. When first touched, make it
passthrough (but not atomically switched) and set a flag (e.g.
"spec_ctrl_live") which triggers the 'restore_branch_speculation' and
'save_and_restrict_branch_speculation' behaviours. Except don't use
those macros. Those can look something like
/* If this vCPU has touched SPEC_CTRL then restore its value if needed */
if (vmx->spec_ctrl_live && vmx->spec_ctrl)
wrmsrl(MSR_IA32_SPEC_CTRL, vmx->spec_ctrl);
/* vmentry is serialising on affected CPUs, so the conditional branch is safe */
... and, respectively, ...
/* If this vCPU has touched SPEC_CTRL then save its value and ensure we have zero */
if (vmx->spec_ctrl_live) {
rdmsrl(MSR_IA32_SPEC_CTRL, vmx->spec_ctrl);
if (vmx->spec_ctrl)
wrmsrl(MSR_IA32_SPEC_CTRL, 0);
}
Perhaps we can ditch the separate 'spec_ctrl_live' flag and check the
pass-through MSR bitmap directly, in the case that it exists?
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-01-29 10:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 0:39 [PATCH] x86: vmx: Allow direct access to MSR_IA32_SPEC_CTRL Liran Alon
2018-01-29 8:46 ` David Woodhouse
2018-01-29 9:43 ` KarimAllah Ahmed
2018-01-29 10:37 ` David Woodhouse [this message]
2018-01-29 10:55 ` Paolo Bonzini
2018-01-29 17:27 ` Konrad Rzeszutek Wilk
2018-01-29 10:47 ` Paolo Bonzini
2018-01-29 17:31 ` Konrad Rzeszutek Wilk
2018-01-29 21:49 ` Daniel Kiper
2018-01-29 23:01 ` Jim Mattson
-- strict thread matches above, loose matches on Subject: below --
2018-01-28 19:29 KarimAllah Ahmed
2018-01-28 20:21 ` Konrad Rzeszutek Wilk
2018-01-28 20:39 ` David Woodhouse
2018-01-28 20:40 ` Andy Lutomirski
2018-01-28 20:44 ` David Woodhouse
2018-01-28 20:53 ` Andy Lutomirski
2018-01-28 20:56 ` David Woodhouse
2018-01-28 21:41 ` Van De Ven, Arjan
2018-01-28 21:47 ` David Woodhouse
2018-01-29 1:06 ` KarimAllah Ahmed
2018-01-29 18:43 ` Jim Mattson
2018-01-29 19:01 ` David Woodhouse
2018-01-29 19:04 ` Jim Mattson
2018-01-29 19:10 ` KarimAllah Ahmed
2018-01-29 19:16 ` Konrad Rzeszutek Wilk
2018-01-29 19:27 ` 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=1517222264.6624.131.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=ashok.raj@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=dan.j.williams@intel.com \
--cc=daniel.kiper@oracle.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jun.nakajima@intel.com \
--cc=karahmed@amazon.com \
--cc=karahmed@amazon.de \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.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