From: Paul Mackerras <paulus@ozlabs.org>
To: kvm@vger.kernel.org, linuxppc-dev@ozlabs.org
Cc: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0/5] KVM & powerpc: Work around POWER9 TM hardware bugs
Date: Wed, 21 Mar 2018 21:28:26 +1100 [thread overview]
Message-ID: <20180321102826.GA13509@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <1521627901-13547-1-git-send-email-paulus@ozlabs.org>
On Wed, Mar 21, 2018 at 09:24:56PM +1100, Paul Mackerras wrote:
> This patch series applies on top of my patch series "powerpc: Free up
> CPU feature bits".
>
> POWER9 has some shortcomings in its implementation of transactional
> memory. Starting with v2.2 of the "Nimbus" chip, some changes have
> been made to the hardware which make it able to generate hypervisor
> interrupts in the situations where hardware needs the hypervisor to
> provide some assistance with the implementation. Specifically, the
> core does not have enough storage to store a complete checkpoint of
> all the architected state for all 4 threads, and therefore needs to
> be able to offload the checkpointed state of threads which are in
> transactional suspended state (for threads that are in transactional
> state, the hardware can simply abort the transaction).
>
> This series implements the hypervisor assistance for TM for KVM
> guests, thus allowing them to use TM. This then means that we can
> allow live migration of guests on POWER8 that may be using TM to
> POWER9 hosts.
>
> This version adds a feature bit for the XER[SO] bug workaround so that
> it can be turned off on future systems which may still require
> hypervisor assistance for TM but have the XER[SO] bug fixed. It also
> makes the test in the idle code (which includes a sync instruction)
> conditional on the XER[SO] bug feature bit, meaning that the code to
> force SMT4 mode will only work when that feature bit is set.
Please ignore this series. I applied a bug fix to the wrong commit.
Paul.
prev parent reply other threads:[~2018-03-21 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 10:24 [PATCH 0/5] KVM & powerpc: Work around POWER9 TM hardware bugs Paul Mackerras
2018-03-21 10:24 ` [PATCH 1/5] powerpc: Add CPU feature bits for TM bug workarounds on POWER9 v2.2 Paul Mackerras
2018-03-21 10:24 ` [PATCH 2/5] powerpc/powernv: Provide a way to force a core into SMT4 mode Paul Mackerras
2018-03-21 10:24 ` [PATCH 3/5] KVM: PPC: Book3S HV: Work around transactional memory bugs in POWER9 Paul Mackerras
2018-03-21 10:25 ` [PATCH 4/5] KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode Paul Mackerras
2018-03-21 10:25 ` [PATCH 5/5] KVM: PPC: Book3S HV: Work around TEXASR bug in fake suspend state Paul Mackerras
2018-03-21 10:28 ` Paul Mackerras [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=20180321102826.GA13509@fergus.ozlabs.ibm.com \
--to=paulus@ozlabs.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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).