From: Cornelia Huck <cohuck@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, "Eduardo Habkost" <ehabkost@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Suraj Jitindar Singh" <sjitindarsingh@gmail.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"Thomas Huth" <thuth@redhat.com>,
"Bruce Rogers" <brogers@suse.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"David Hildenbrand" <david@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH v2] Add a blog post documenting Spectre/Meltdown options for QEMU 2.11.1
Date: Wed, 14 Feb 2018 17:38:58 +0100 [thread overview]
Message-ID: <20180214173858.464f4c59.cohuck@redhat.com> (raw)
In-Reply-To: <20180214161213.7894-1-mdroth@linux.vnet.ibm.com>
On Wed, 14 Feb 2018 10:12:13 -0600
Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
> This blog entry is intended as a follow-up to the original entry in
> January regarding Spectre/Meltdown and the proposed changes to address
> them in the upcoming 2.11.1 release.
>
> This entry is meant to accompany the 2.11.1 release (planned for
> 2018-02-14) and document how to make use of the new options for
> various architectures.
>
> Cc: Eduardo Habkost <ehabkost@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
> Cc: David Gibson <david@gibson.dropbear.id.au>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Cornelia Huck <cohuck@redhat.com>
> Cc: Thomas Huth <thuth@redhat.com>
> Cc: Bruce Rogers <brogers@suse.com>
> Cc: Daniel P. Berrangé <berrange@redhat.com>
> Cc: David Hildenbrand <david@redhat.com>
> Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> ---
> v2:
> * s/by itself that/by itself for that/ (Bruce)
> * make example formats more consistent (Bruce)
> * clarify wording WRT to host-side security (Daniel, Paolo)
> * general wording/formatting fix-ups (Thomas)
> * s/options/feature bits/ (Cornelia)
> * clarify s390x CPU feature defaults (Thomas/Cornelia/Christian/David)
> * clarify s390x migration compatibility statement (Cornelia)
>
> Thank you for the review!
Thank you for writing this blog post!
>
> .../2018-02-14-qemu-2-11-1-and-spectre-update.md | 190 +++++++++++++++++++++
> 1 file changed, 190 insertions(+)
> create mode 100644 _posts/2018-02-14-qemu-2-11-1-and-spectre-update.md
> +## Enabling mitigation features for s390x KVM guests
> +
> +For s390x guests there are 2 CPU feature bits relating to Spectre/Meltdown:
> +
> +* bpb: Branch prediction blocking
> +* ppa15: PPA15 is installed
> +
> +**bpb** requires a host kernel patched with:
> +
> + commit 35b3fde6203b932b2b1a5b53b3d8808abc9c4f60
> + KVM: s390: wire up bpb feature
> +
> +and both **bpb** and **ppa15** require a firmware with the appropriate support
> +level as well as guest kernel patches to enable the functionality within
> +guests. Please check with your distro/vendor to confirm.
> +
> +Both **bpb** and **ppa15** are enabled by default with newer/patched host
> +kernels, and can also be set manually. For example:
> +
> + qemu-system-s390x -M s390-ccw-virtio-2.11 ... \
> + -cpu zEC12,bpb=on,ppa15=on
> +
> +Both **bpb** and **ppa15** are enabled by default when using "-cpu host"
> +and when the host kernels supports these facilities. For other CPU
> +models, the flags have to be set manually. For example:
> +
> + qemu-system-s390x -M s390-ccw-virtio-2.11 ... \
> + -cpu zEC12,bpb=on,ppa15=on
> +
> +With regard to migration, enabling **bpb** or **ppa15** feature flags requires
> +that the source/target also those flags enabled.
s/also those/also has those/
> Since this is enabled by
> +default for '-cpu host' (when available on the host), you must ensure that
> +**bpb**=off,**ppa15**=off is used if you wish to maintain migration
> +compatibility with existing guests when using '-cpu host', or take steps to
> +reboot guests with **bpb**/**ppa15** enabled prior to migration.
Otherwise, s390 part looks good to me.
prev parent reply other threads:[~2018-02-14 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 16:12 [Qemu-devel] [qemu-web PATCH v2] Add a blog post documenting Spectre/Meltdown options for QEMU 2.11.1 Michael Roth
2018-02-14 16:38 ` Cornelia Huck [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=20180214173858.464f4c59.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=brogers@suse.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sjitindarsingh@gmail.com \
--cc=thuth@redhat.com \
/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).