[PATCH v3 0/2] arm64: Allow erratum 1418040 for late CPUs

Doug Anderson dianders at google.com
Wed Sep 9 10:53:25 EDT 2020


Hi,

On Fri, Aug 21, 2020 at 11:15 AM Catalin Marinas
<catalin.marinas at arm.com> wrote:
>
> On Fri, 31 Jul 2020 18:38:22 +0100, Marc Zyngier wrote:
> > Erratum 1418040 currently prevents a late CPU from booting if none
> > of the early CPUs are affected by it. This is because the handling
> > is implemented as alternatives, and we have already got rid of them
> > by the time userspace onlines a new CPU.
> >
> > A solution to this is to move everything into C code, and rely on
> > static keys instead. Once this is done, the feature can be allowed
> > for late CPUs.
> >
> > [...]
>
> Applied to arm64 (for-next/fixes), thanks!
>
> [1/2] arm64: Move handling of erratum 1418040 into C code
>       https://git.kernel.org/arm64/c/d49f7d7376d0
> [2/2] arm64: Allow booting of late CPUs affected by erratum 1418040
>       https://git.kernel.org/arm64/c/bf87bb0881d0

NOTE: patch 2 seems to have come in through a stable merge onto Chrome
OS 5.4 and is causing a regression when resuming from suspend.  In the
short term we've got a revert going into our tree:

https://crrev.com/c/2399101

...but that's obviously not a long term fix.  I haven't done any
debugging of this myself, though I can if there's nobody more
qualified to do it and/or nobody else has time.  I'm just trying to
make sure that the problem is reported somewhere where others might
notice it rather than in an obscure Chrome OS tree.  ;-)

-Doug



More information about the linux-arm-kernel mailing list