From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add check for Cortex-A15 errata 798181 ECO
Date: Mon, 15 Jul 2013 23:22:26 +0100 [thread overview]
Message-ID: <20130715222226.GX24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMjATn9MCzazUGmbD44XR8HyJZU4cCvmOEoUZsmCgutPUg@mail.gmail.com>
On Mon, Jul 15, 2013 at 01:59:24PM -0700, Olof Johansson wrote:
> On Mon, Jul 15, 2013 at 1:42 PM, Rob Herring <robherring2@gmail.com> wrote:
> > diff --git a/arch/arm/kernel/smp_tlb.c b/arch/arm/kernel/smp_tlb.c
> > index 9a52a07..7fd64b7 100644
> > --- a/arch/arm/kernel/smp_tlb.c
> > +++ b/arch/arm/kernel/smp_tlb.c
> > @@ -74,10 +74,21 @@ static inline void ipi_flush_bp_all(void *ignored)
> > static int erratum_a15_798181(void)
> > {
> > unsigned int midr = read_cpuid_id();
> > + unsigned int revidr;
> >
> > /* Cortex-A15 r0p0..r3p2 affected */
> > if ((midr & 0xff0ffff0) != 0x410fc0f0 || midr > 0x413fc0f2)
> > return 0;
> > +
> > + /* Check for Cortex A15 <= r3p2 with ECO fix */
> > + revidr = read_cpuid(CPUID_REVIDR);
> > + if ((revidr & 0x210) == 0x210)
> > + return 0;
>
> Reading and evaluating all this on every invalidate seems suboptimal.
> It should be possible to read just once and cache the result.
>
> I would have had the same comment about the original patch, but ARM
> pushes those to Russell in secret so it wasn't on the list. :-)
For a single read, there's probably not much between reading the CP15
register and doing the tests, vs reading a bool from memory to decide
whether we need to do it.
For more than that (as the above patch is growing) it probably makes
sense to think about using a bool in memory now.
prev parent reply other threads:[~2013-07-15 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 20:42 [PATCH] ARM: Add check for Cortex-A15 errata 798181 ECO Rob Herring
2013-07-15 20:59 ` Olof Johansson
2013-07-15 22:08 ` Rob Herring
2013-07-15 22:22 ` Russell King - ARM Linux [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=20130715222226.GX24642@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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