From: Ard Biesheuvel <ardb@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: linux-efi <linux-efi@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <maz@kernel.org>, Nicolas Pitre <nico@fluxnic.net>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH 1/2] ARM: decompressor: prepare cache_clean_flush for doing by-VA maintenance
Date: Tue, 18 Feb 2020 17:56:52 +0100 [thread overview]
Message-ID: <CAKv+Gu_90hPPupcPCkURqBe2xFO0Zv96egytOPcqLF5XLf-rbQ@mail.gmail.com> (raw)
In-Reply-To: <20200218165149.GK25745@shell.armlinux.org.uk>
On Tue, 18 Feb 2020 at 17:52, Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
>
> On Tue, Feb 18, 2020 at 05:44:29PM +0100, Ard Biesheuvel wrote:
> > In preparation of turning the decompressor's cache clean/flush
> > operations into proper by-VA maintenance for v7 cores, pass the
> > start and end addresses of the regions that need cache maintenance
> > into cache_clean_flush in registers r0 and r1.
>
> Where's the documentation of the new calling convention? This is
> assembly code, it needs such things documented as there's no
> function prototypes to give that information.
>
Would something like
diff --git a/arch/arm/boot/compressed/head.S b/arch/arm/boot/compressed/head.S
index df93c9f0a19a..e4c779a89db1 100644
--- a/arch/arm/boot/compressed/head.S
+++ b/arch/arm/boot/compressed/head.S
@@ -1207,6 +1207,9 @@ __armv7_mmu_cache_off:
/*
* Clean and flush the cache to maintain consistency.
*
+ * On entry,
+ * r0 = start address
+ * r1 = end address (exclusive)
* On exit,
* r1, r2, r3, r9, r10, r11, r12 corrupted
* This routine must preserve:
work for you?
> >
> > Currently, all implementations of cache_clean_flush ignore these
> > values, so no functional change is expected as a result of this
> > patch.
> >
> > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > ---
> > arch/arm/boot/compressed/head.S | 28 +++++++++++++++++---
> > 1 file changed, 25 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm/boot/compressed/head.S b/arch/arm/boot/compressed/head.S
> > index 7b86a2e1acce..935799b92198 100644
> > --- a/arch/arm/boot/compressed/head.S
> > +++ b/arch/arm/boot/compressed/head.S
> > @@ -525,12 +525,15 @@ dtb_check_done:
> > /* cache_clean_flush may use the stack, so relocate it */
> > add sp, sp, r6
> > #endif
> > -
> > + mov r0, r9
> > + ldr r1, 0f
> > + add r1, r1, r0
> > bl cache_clean_flush
> >
> > badr r0, restart
> > add r0, r0, r6
> > mov pc, r0
> > +0: .long _edata - restart
> >
> > wont_overwrite:
> > /*
> > @@ -622,6 +625,21 @@ not_relocated: mov r0, #0
> > add r2, sp, #0x10000 @ 64k max
> > mov r3, r7
> > bl decompress_kernel
> > +
> > + mov r0, r4 @ base of inflated image
> > + adr r1, LC0 @ actual LC0
> > + ldr r2, [r1] @ linktime LC0
> > + sub r2, r1, r2 @ LC0 delta
> > + ldr r1, [r1, #16] @ link time inflated size offset
> > + ldr r1, [r1, r2] @ actual inflated size (LE)
> > +#ifdef __ARMEB__
> > + /* convert to big endian */
> > + eor r2, r1, r1, ror #16
> > + bic r2, r2, #0x00ff0000
> > + mov r1, r1, ror #8
> > + eor r1, r1, r2, lsr #8
> > +#endif
> > + add r1, r1, r0 @ end of inflated image
> > bl cache_clean_flush
> > bl cache_off
> >
> > @@ -1439,6 +1457,7 @@ reloc_code_end:
> > #ifdef CONFIG_EFI_STUB
> > .align 2
> > _start: .long start - .
> > +__edata: .long _edata - .
> >
> > ENTRY(efi_stub_entry)
> > @ allocate space on stack for passing current zImage address
> > @@ -1470,8 +1489,11 @@ ENTRY(efi_stub_entry)
> > .align 2
> > 0: .long start - (. + 4)
> >
> > - @ Preserve return value of efi_entry() in r4
> > - mov r4, r0
> > + mov r4, r0 @ preserve DTB pointer
> > + mov r0, r1 @ start of image
> > + adr r2, __edata
> > + ldr r1, [r2]
> > + add r1, r1, r2 @ end of image
> > bl cache_clean_flush
> > bl cache_off
> >
> > --
> > 2.17.1
> >
> >
>
> --
> 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
next prev parent reply other threads:[~2020-02-18 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 16:44 [PATCH 0/2] ARM: decompressor: use by-VA cache maintenance for v7 cores Ard Biesheuvel
2020-02-18 16:44 ` [PATCH 1/2] ARM: decompressor: prepare cache_clean_flush for doing by-VA maintenance Ard Biesheuvel
2020-02-18 16:51 ` Russell King - ARM Linux admin
2020-02-18 16:56 ` Ard Biesheuvel [this message]
2020-02-18 17:08 ` Russell King - ARM Linux admin
2020-02-18 16:44 ` [PATCH 2/2] ARM: decompressor: switch to by-VA cache maintenance for v7 cores 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=CAKv+Gu_90hPPupcPCkURqBe2xFO0Zv96egytOPcqLF5XLf-rbQ@mail.gmail.com \
--to=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maz@kernel.org \
--cc=nico@fluxnic.net \
/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).