public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	x86@kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
	"KarimAllah Ahmed" <karahmed@amazon.de>,
	"David Woodhouse" <dwmw@amazon.co.uk>,
	"Jim Mattson" <jmattson@google.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@kernel.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/3] KVM: x86: use native MSR ops for SPEC_CTRL
Date: Fri, 23 Feb 2018 18:35:30 +0100	[thread overview]
Message-ID: <7534bcd3-e21b-240c-9ed2-62026ba10301@redhat.com> (raw)
In-Reply-To: <20180223172220.GK8252@char.us.oracle.com>

On 23/02/2018 18:22, Konrad Rzeszutek Wilk wrote:
> On Fri, Feb 23, 2018 at 10:37:49AM +0100, Paolo Bonzini wrote:
>> On 22/02/2018 18:07, Konrad Rzeszutek Wilk wrote:
>>>> Having a paravirt indirect call in the IBRS restore path is not a
>>>> good idea, since we are trying to protect from speculative execution
>>>> of bogus indirect branch targets.  It is also slower, so use
>>>> native_wrmsrl on the vmentry path too.
>>> But it gets replaced during patching. As in once the machine boots
>>> the assembler changes from:
>>>
>>> 	callq 	*0xfffflbah
>>>
>>> to
>>> 	wrmsr
>>>
>>> ? I don't think you need this patch.
>>
>> Why not be explicit?  According to the spec, PRED_CMD and SPEC_CTRL
> 
> Explicit is fine.
> 
> But I would recommend you change the commit message to say so, and
> perhaps remove 'It is also slower' - as that is incorrect.

Actually it is faster---that's why I made the change in the first place,
though later I noticed

> If it is detected to be Xen PV, then yes
> it will be a call to a function. But that won't help as Xen PV runs in
> ring 3, so it has a whole bunch of other issues.

Ok, I wasn't sure about PVH (which runs in ring 0 afair).

Paolo

  reply	other threads:[~2018-02-23 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 21:41 [PATCH 0/3] x86/pti: KVM: fixes and optimizations for IBRS Paolo Bonzini
2018-02-21 21:41 ` [PATCH 1/3] KVM: x86: use native MSR ops for SPEC_CTRL Paolo Bonzini
2018-02-21 23:49   ` Jim Mattson
2018-02-22 17:07   ` Konrad Rzeszutek Wilk
2018-02-23  9:37     ` Paolo Bonzini
2018-02-23 17:22       ` Konrad Rzeszutek Wilk
2018-02-23 17:35         ` Paolo Bonzini [this message]
2018-02-23 17:55           ` Konrad Rzeszutek Wilk
2018-02-21 21:41 ` [PATCH 2/3] KVM: nVMX: fix wrong condition for SPEC_CTRL and PRED_CMD MSRs Paolo Bonzini
2018-02-22  0:07   ` Jim Mattson
2018-02-22  9:39     ` Paolo Bonzini
2018-02-21 21:41 ` [PATCH 3/3] KVM: VMX: mark RDMSR path as unlikely Paolo Bonzini
2018-02-22  0:25   ` 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=7534bcd3-e21b-240c-9ed2-62026ba10301@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dwmw@amazon.co.uk \
    --cc=jmattson@google.com \
    --cc=karahmed@amazon.de \
    --cc=konrad.wilk@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rkrcmar@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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