From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
linux-efi <linux-efi@vger.kernel.org>,
Vladimir Murzin <vladimir.murzin@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] efi/arm: enable CP15 DMB instructions before cleaning the cache
Date: Fri, 12 Apr 2019 21:58:34 +0100 [thread overview]
Message-ID: <20190412205834.aok6v3fnjaxl27qt@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAKv+Gu_Fj9BacvCwu3XdWgE_i4EZWpTAp2Jjhj4DGMzC0bo1nA@mail.gmail.com>
On Fri, Apr 12, 2019 at 01:38:12PM -0700, Ard Biesheuvel wrote:
> On Tue, 9 Apr 2019 at 09:42, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> >
> > The EFI stub is entered with the caches and MMU enabled by the
> > firmware, and once the stub is ready to hand over to the decompressor,
> > we clean and disable the caches.
> >
> > The cache clean routines use CP15 barrier instructions, which can be
> > disabled via SCTLR. Normally, when using the provided cache handling
> > routines to enable the caches and MMU, this bit is enabled as well.
> > However, but since we entered the stub with the caches already enabled,
> > this routine is not executed before we call the cache clean routines,
> > resulting in undefined instruction exceptions if the firmware never
> > enabled this bit.
> >
> > So set the bit explicitly in the EFI entry code, but do so in a way that
> > guarantees that the resulting code can still run on v6 cores as well
> > (which are guaranteed to have CP15 barriers enabled)
> >
> > Acked-by: Marc Zyngier <marc.zyngier@arm.com>
> > Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > ---
> > arch/arm/boot/compressed/head.S | 16 +++++++++++++++-
> > 1 file changed, 15 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/boot/compressed/head.S b/arch/arm/boot/compressed/head.S
> > index 6c7ccb428c07..c174098acdf1 100644
> > --- a/arch/arm/boot/compressed/head.S
> > +++ b/arch/arm/boot/compressed/head.S
> > @@ -1438,7 +1438,21 @@ ENTRY(efi_stub_entry)
> >
> > @ Preserve return value of efi_entry() in r4
> > mov r4, r0
> > - bl cache_clean_flush
> > +
> > + @ our cache maintenance code relies on CP15 barrier instructions
> > + @ but since we arrived here with the MMU and caches configured
> > + @ by UEFI, we must check that the CP15BEN bit is set in SCTLR.
> > + @ Note that this bit is RAO/WI on v6 and earlier, so the ISB in
> > + @ the enable path will be executed on v7+ only.
> > + mrc p15, 0, r1, c1, c0, 0 @ read SCTLR
> > + tst r1, #(1 << 5) @ CP15BEN bit set?
> > + bne 0f
> > + orr r1, r1, #(1 << 5) @ CP15 barrier instructions
> > + mcr p15, 0, r1, c1, c0, 0 @ write SCTLR
> > + ARM( .inst 0xf57ff06f @ isb )
> > + THUMB( isb )
> > +
> > +0: bl cache_clean_flush
> > bl cache_off
> >
> > @ Set parameters for booting zImage according to boot protocol
> > --
> > 2.17.1
> >
>
> Russell, do you mind if I take this through the EFI tree?
Yes I do mind.
> I had trouble logging into your patch system (it no longer recognizes my
> email address
I can't debug it based on that - what does it say?
> but when I try to re-create the account, my name is already taken)
Yes, duplicate accounts can't be created, but there is also a forgotten
password feature.
I've just checked and I can log in fine.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-12 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 16:42 [PATCH v2] efi/arm: enable CP15 DMB instructions before cleaning the cache Ard Biesheuvel
2019-04-12 20:38 ` Ard Biesheuvel
2019-04-12 20:58 ` Russell King - ARM Linux admin [this message]
2019-04-12 21:00 ` Ard Biesheuvel
2019-04-12 21:20 ` Russell King - ARM Linux admin
2019-04-12 21:21 ` Ard Biesheuvel
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=20190412205834.aok6v3fnjaxl27qt@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=vladimir.murzin@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox