From: Eduardo Habkost <ehabkost@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/3] x86: Haswell TSX blacklist fix for 2.9
Date: Fri, 10 Mar 2017 15:45:49 -0300 [thread overview]
Message-ID: <20170310184552.1481-1-ehabkost@redhat.com> (raw)
The following changes since commit dd4d2578215cd380f40a38028a9904e15b135ef3:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-fixes-20170309-1' into staging (2017-03-09 13:16:05 +0000)
are available in the git repository at:
git://github.com/ehabkost/qemu.git tags/x86-pull-request
for you to fetch changes up to ec56a4a7b07e2943f49da273a31e3195083b1f2e:
i386: Change stepping of Haswell to non-blacklisted value (2017-03-10 15:01:09 -0300)
----------------------------------------------------------------
x86: Haswell TSX blacklist fix for 2.9
----------------------------------------------------------------
Eduardo Habkost (3):
i386: host_vendor_fms() helper function
i386/kvm: Blacklist TSX on known broken hosts
i386: Change stepping of Haswell to non-blacklisted value
include/hw/i386/pc.h | 5 +++++
target/i386/cpu.h | 1 +
target/i386/cpu.c | 21 ++++++++++++++++++++-
target/i386/kvm.c | 17 +++++++++++++++++
4 files changed, 43 insertions(+), 1 deletion(-)
--
2.11.0.259.g40922b1
next reply other threads:[~2017-03-10 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 18:45 Eduardo Habkost [this message]
2017-03-10 18:45 ` [Qemu-devel] [PULL 1/3] i386: host_vendor_fms() helper function Eduardo Habkost
2017-03-10 18:45 ` [Qemu-devel] [PULL 2/3] i386/kvm: Blacklist TSX on known broken hosts Eduardo Habkost
2017-03-10 18:45 ` [Qemu-devel] [PULL 3/3] i386: Change stepping of Haswell to non-blacklisted value Eduardo Habkost
2017-03-13 15:08 ` [Qemu-devel] [PULL 0/3] x86: Haswell TSX blacklist fix for 2.9 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=20170310184552.1481-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).