From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Cc: Eirik Fuller <efuller@redhat.com>, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH v1 1/2] powerpc/64s: system call rfscv workaround for TM bugs
Date: Sun, 19 Sep 2021 22:20:28 +1000 [thread overview]
Message-ID: <163205402834.1052045.16310536368273936213.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210908101718.118522-1-npiggin@gmail.com>
On Wed, 8 Sep 2021 20:17:17 +1000, Nicholas Piggin wrote:
> The rfscv instruction does not work correctly with the fake-suspend mode
> in POWER9, which can end up with the hypervisor restoring an incorrect
> checkpoint.
>
> Work around this by setting the _TIF_RESTOREALL flag if a system call
> returns to a transaction active state, causing rfid to be used instead
> of rfscv to return, which will do the right thing. The contents of the
> registers are irrelevant because they will be overwritten in this case
> anyway.
>
> [...]
Applied to powerpc/fixes.
[1/2] powerpc/64s: system call rfscv workaround for TM bugs
https://git.kernel.org/powerpc/c/ae7aaecc3f2f78b76ab3a8d6178610f55aadfa56
[2/2] KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing registers
https://git.kernel.org/powerpc/c/267cdfa21385d78c794768233678756e32b39ead
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: linuxppc-dev@lists.ozlabs.org, Nicholas Piggin <npiggin@gmail.com>
Cc: Eirik Fuller <efuller@redhat.com>, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH v1 1/2] powerpc/64s: system call rfscv workaround for TM bugs
Date: Sun, 19 Sep 2021 12:20:28 +0000 [thread overview]
Message-ID: <163205402834.1052045.16310536368273936213.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20210908101718.118522-1-npiggin@gmail.com>
On Wed, 8 Sep 2021 20:17:17 +1000, Nicholas Piggin wrote:
> The rfscv instruction does not work correctly with the fake-suspend mode
> in POWER9, which can end up with the hypervisor restoring an incorrect
> checkpoint.
>
> Work around this by setting the _TIF_RESTOREALL flag if a system call
> returns to a transaction active state, causing rfid to be used instead
> of rfscv to return, which will do the right thing. The contents of the
> registers are irrelevant because they will be overwritten in this case
> anyway.
>
> [...]
Applied to powerpc/fixes.
[1/2] powerpc/64s: system call rfscv workaround for TM bugs
https://git.kernel.org/powerpc/c/ae7aaecc3f2f78b76ab3a8d6178610f55aadfa56
[2/2] KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing registers
https://git.kernel.org/powerpc/c/267cdfa21385d78c794768233678756e32b39ead
cheers
next prev parent reply other threads:[~2021-09-19 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 10:17 [PATCH v1 1/2] powerpc/64s: system call rfscv workaround for TM bugs Nicholas Piggin
2021-09-08 10:17 ` Nicholas Piggin
2021-09-08 10:17 ` [PATCH v1 2/2] KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing registers Nicholas Piggin
2021-09-08 10:17 ` Nicholas Piggin
2021-09-17 8:02 ` [PATCH v1 1/2] powerpc/64s: system call rfscv workaround for TM bugs Daniel Axtens
2021-09-17 8:02 ` Daniel Axtens
2021-09-19 12:20 ` Michael Ellerman [this message]
2021-09-19 12:20 ` Michael Ellerman
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=163205402834.1052045.16310536368273936213.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=efuller@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.