From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fix midr range for Cortex-A57 erratum 832075
Date: Wed, 1 Apr 2015 10:22:29 +0100 [thread overview]
Message-ID: <20150401092229.GC1552@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503312113340.24011@utopia.booyaka.com>
On Tue, Mar 31, 2015 at 10:17:21PM +0100, Paul Walmsley wrote:
> On Tue, 31 Mar 2015, Bo Yan wrote:
>
> > Register MIDR_EL1 is masked to get variant and revision fields, then
> > compared against midr_range_min and midr_range_max when checking
> > whether CPU is affected by any particular erratum. However, variant
> > and revision fields in MIDR_EL1 are separated by 16 bits, so the min
> > and max of midr range should be constructed accordingly, otherwise
> > the patch will not be applied when variant field is non-0.
> >
> > Signed-off-by: Bo Yan <byan@nvidia.com>
> > ---
> > arch/arm64/kernel/cpu_errata.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
> > index fa62637e63a8..7838f1578019 100644
> > --- a/arch/arm64/kernel/cpu_errata.c
> > +++ b/arch/arm64/kernel/cpu_errata.c
> > @@ -88,7 +88,7 @@ struct arm64_cpu_capabilities arm64_errata[] = {
> > /* Cortex-A57 r0p0 - r1p2 */
> > .desc = "ARM erratum 832075",
> > .capability = ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE,
> > - MIDR_RANGE(MIDR_CORTEX_A57, 0x00, 0x12),
> > + MIDR_RANGE(MIDR_CORTEX_A57, 0x00, 0x100002),
> > },
> > #endif
> > {
> > --
> > 2.1.4
>
> Reviewed-by: Paul Walmsley <paul@pwsan.com>
>
> Reviewed against DDI0488G section 4.3.1 "Main ID Register, EL1". Looks
> like a cut-and-paste error from the A53 workarounds.
Thanks guys, I agree that this is a bug. I'll apply this, but using an
explicit shift to set the variant (tweaked version below).
Will
--->8
diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
index a66f4fa4d541..c998345a052f 100644
--- a/arch/arm64/kernel/cpu_errata.c
+++ b/arch/arm64/kernel/cpu_errata.c
@@ -70,7 +70,7 @@ const struct arm64_cpu_capabilities arm64_errata[] = {
/* Cortex-A57 r0p0 - r1p2 */
.desc = "ARM erratum 832075",
.capability = ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE,
- MIDR_RANGE(MIDR_CORTEX_A57, 0x00, 0x12),
+ MIDR_RANGE(MIDR_CORTEX_A57, 0x00, (1 << MIDR_VARIANT_SHIFT) | 2,
},
#endif
{
next prev parent reply other threads:[~2015-04-01 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 20:30 [PATCH] arm64: fix midr range for Cortex-A57 erratum 832075 Bo Yan
2015-03-31 21:17 ` Paul Walmsley
2015-04-01 9:22 ` Will Deacon [this message]
2015-04-01 9:27 ` Andre Przywara
2015-04-01 9:29 ` Will Deacon
2015-04-01 10:55 ` Mark Rutland
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=20150401092229.GC1552@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).