From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] how to pass pcid to guest?
Date: Wed, 10 Jan 2018 13:02:05 +0000 [thread overview]
Message-ID: <20180110130205.GN3205@redhat.com> (raw)
In-Reply-To: <a094668d-3294-e4b8-47a0-08ed8da5f9df@redhat.com>
On Mon, Jan 08, 2018 at 04:07:53PM -0600, Eric Blake wrote:
> On 01/08/2018 02:03 PM, Stefan Priebe - Profihost AG wrote:
> > Hello,
> >
> > for meltdown mitigation and performance it's important to have the pcid
> > flag passed down to the guest (f.e.
> > https://groups.google.com/forum/m/#!topic/mechanical-sympathy/L9mHTbeQLNU).
>
> Indeed; you are still waiting on the qemu patch mentioned here:
> https://www.qemu.org/2018/01/04/spectre/
>
> which is still undergoing the review process, but should be up (in the
> form of 2.11.1) "in the next few days".
There's two different things here. The Spectre patch you mention is about
exposing a new CPUID feature 'ibrs' that is added to fix Spectre. The 'pcid'
feature Stefan mentions is a pre-existing feature that is not a security fix,
but rather a way to improve the performance when the KAISER/KPTI patches are
enabled for Meltdown.
'pcid' is available in QEMU's Haswell, Broadwell & Skylake based CPU
models by default. For other named CPU models, you can turn it on using
',+pcid' after the model name. eg '-cpu Westmere,+pcid' (as long as your
host supports it of course)
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2018-01-10 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 20:03 [Qemu-devel] how to pass pcid to guest? Stefan Priebe - Profihost AG
2018-01-08 22:07 ` Eric Blake
2018-01-09 13:12 ` Stefan Priebe - Profihost AG
2018-01-10 13:02 ` Daniel P. Berrange [this message]
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=20180110130205.GN3205@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=s.priebe@profihost.ag \
/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).