From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: maz@kernel.org, marc.zyngier@arm.com, stable@vger.kernel.org,
will@kernel.org
Subject: Re: FAILED: patch "[PATCH] arm64: Avoid Cavium TX2 erratum 219 when switching TTBR" failed to apply to 4.19-stable tree
Date: Mon, 28 Oct 2019 05:12:07 -0400 [thread overview]
Message-ID: <20191028091207.GL1560@sasha-vm> (raw)
In-Reply-To: <157218441316235@kroah.com>
On Sun, Oct 27, 2019 at 02:53:33PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 9405447ef79bc93101373e130f72e9e6cbf17dbb Mon Sep 17 00:00:00 2001
>From: Marc Zyngier <maz@kernel.org>
>Date: Tue, 9 Apr 2019 16:22:24 +0100
>Subject: [PATCH] arm64: Avoid Cavium TX2 erratum 219 when switching TTBR
>
>As a PRFM instruction racing against a TTBR update can have undesirable
>effects on TX2, NOP-out such PRFM on cores that are affected by
>the TX2-219 erratum.
>
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>Signed-off-by: Will Deacon <will@kernel.org>
Rather than backporting this, we need to look into backporting the rest
of the errata fixes. I'll look into that...
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-10-28 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 13:53 FAILED: patch "[PATCH] arm64: Avoid Cavium TX2 erratum 219 when switching TTBR" failed to apply to 4.19-stable tree gregkh
2019-10-28 9:12 ` Sasha Levin [this message]
2019-10-28 10:53 ` Marc Zyngier
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=20191028091207.GL1560@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=marc.zyngier@arm.com \
--cc=maz@kernel.org \
--cc=stable@vger.kernel.org \
--cc=will@kernel.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).