From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PULL 0/3] x86 MDS feature flags
Date: Tue, 21 May 2019 15:50:56 -0300 [thread overview]
Message-ID: <20190521185059.28236-1-ehabkost@redhat.com> (raw)
The following changes since commit a4f667b6714916683408b983cfe0a615a725775f:
Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190521-3' into staging (2019-05-21 16:30:13 +0100)
are available in the Git repository at:
git://github.com/ehabkost/qemu.git tags/x86-next-pull-request
for you to fetch changes up to 20140a82c67467f53814ca197403d5e1b561a5e5:
target/i386: add MDS-NO feature (2019-05-21 15:39:05 -0300)
----------------------------------------------------------------
x86 MDS feature flags
md-clear and mds-no feature flags, for detection and mitigation
of MDS vulnerabilities (CVE-2018-12126, CVE-2018-12127,
CVE-2018-12130, CVE-2019-11091).
----------------------------------------------------------------
Daniel P. Berrangé (1):
docs: recommend use of md-clear feature on all Intel CPUs
Paolo Bonzini (2):
target/i386: define md-clear bit
target/i386: add MDS-NO feature
docs/qemu-cpu-models.texi | 12 ++++++++++++
target/i386/cpu.c | 4 ++--
2 files changed, 14 insertions(+), 2 deletions(-)
--
2.18.0.rc1.1.g3f1ff2140
next reply other threads:[~2019-05-21 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 18:50 Eduardo Habkost [this message]
2019-05-21 18:50 ` [Qemu-devel] [PULL 1/3] target/i386: define md-clear bit Eduardo Habkost
2019-05-21 18:50 ` [Qemu-devel] [PULL 2/3] docs: recommend use of md-clear feature on all Intel CPUs Eduardo Habkost
2019-05-21 18:50 ` [Qemu-devel] [PULL 3/3] target/i386: add MDS-NO feature Eduardo Habkost
2019-05-23 8:55 ` [Qemu-devel] [PULL 0/3] x86 MDS feature flags 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=20190521185059.28236-1-ehabkost@redhat.com \
--to=ehabkost@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;
as well as URLs for NNTP newsgroup(s).