public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [PULL 4/4] i386: Add "stibp" flag name
Date: Wed, 12 Dec 2018 15:11:51 -0200	[thread overview]
Message-ID: <20181212171151.GW7141@habkost.net> (raw)
In-Reply-To: <20181212170110.GJ31033@redhat.com>

On Wed, Dec 12, 2018 at 05:01:10PM +0000, Daniel P. Berrangé wrote:
> On Wed, Dec 12, 2018 at 04:57:42PM +0000, Lendacky, Thomas wrote:
> > On 12/11/2018 02:53 PM, Eduardo Habkost wrote:
> > > The STIBP flag may be supported by the host KVM module, so QEMU
> > > can allow it to be configured manually, and it can be exposed to
> > > guests when using "-cpu host".
> > > 
> > > No additional migration code is required because the whole
> > > contents of spec_ctrl is already migrated in the "cpu/spec_ctrl"
> > > section.
> > > 
> > > Corresponding KVM patch was submitted at:
> > > https://lore.kernel.org/lkml/20181205191956.31480-1-ehabkost@redhat.com/
> > > 
> > > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > > Message-Id: <20181210180250.31299-1-ehabkost@redhat.com>
> > > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> > > ---
> > >  target/i386/cpu.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > > index 86a934d450..12f559b6af 100644
> > > --- a/target/i386/cpu.c
> > > +++ b/target/i386/cpu.c
> > > @@ -1042,7 +1042,7 @@ static FeatureWordInfo feature_word_info[FEATURE_WORDS] = {
> > >              NULL, NULL, NULL, NULL,
> > >              NULL, NULL, "pconfig", NULL,
> > >              NULL, NULL, NULL, NULL,
> > > -            NULL, NULL, "spec-ctrl", NULL,
> > > +            NULL, NULL, "spec-ctrl", "stibp",
> > 
> > I guess I missed this earlier. Is there a corresponding patch for the AMD
> > STIBP bit (CPUID 0x80000008_EBX[15]) that is in KVM?
> 
> This Intel STIBP patch is one that many distros have carried downstream
> since the flaw came to light.
> 
> I've not seen any equiv patch for AMD STIBP bit, in either QMEU or libvirt,
> so guess that's a gap that needs filling.

I can submit a "amd-stibp" patch for completeness, although I
doubt many people will actually use the flag.

-- 
Eduardo

  reply	other threads:[~2018-12-12 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 20:53 [PULL 0/4] x86 queue, 2018-12-11 Eduardo Habkost
2018-12-11 20:53 ` [PULL 1/4] x86/cpu: Enable MOVDIRI cpu feature Eduardo Habkost
2018-12-11 20:53 ` [PULL 2/4] x86/cpu: Enable MOVDIR64B " Eduardo Habkost
2018-12-11 20:53 ` [PULL 3/4] target/i386/kvm.c: Don't mark cpuid_data as QEMU_PACKED Eduardo Habkost
2018-12-11 20:53 ` [PULL 4/4] i386: Add "stibp" flag name Eduardo Habkost
2018-12-12 16:57   ` Lendacky, Thomas
2018-12-12 17:01     ` Daniel P. Berrangé
2018-12-12 17:11       ` Eduardo Habkost [this message]
2018-12-13  9:27 ` [PULL 0/4] x86 queue, 2018-12-11 Peter Maydell

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=20181212171151.GW7141@habkost.net \
    --to=ehabkost@redhat.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=berrange@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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