The EFI stub in the ARM kernel runs in the context of the firmware, which means it runs with the caches and MMU on. Currently, we relocate the zImage so it appears in the first 128 MiB, disable the MMU and caches and invoke the decompressor via its ordinary entry point. However, since we can pass the base of DRAM directly, there is no need to relocate the zImage, which also means there is no need to disable and re-enable the caches and create new page tables etc. This simplification is implemented by patch #5. Patches #1 - #4 are prerequisite changes to permit the decompressor to execute from the offset chosen by the UEFI firmware. Note that this applies onto linux-next with Geert's patch 'ARM: boot: Obtain start of physical memory from DTB' applied [0] Cc: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> Cc: Nicolas Pitre <nico@xxxxxxxxxxx> Cc: Linus Walleij <linus.walleij@xxxxxxxxxx> Cc: Russell King <linux@xxxxxxxxxxxxxxx> [0] https://lore.kernel.org/linux-arm-kernel/20200320144348.12865-1-geert+renesas@xxxxxxxxx/ Ard Biesheuvel (5): ARM: decompressor: move headroom variable out of LC0 ARM: decompressor: split off _edata and stack base into separate object ARM: decompressor: defer loading of the contents of the LC0 structure ARM: decompressor: move GOT into .data for EFI enabled builds ARM: decompressor: run decompressor in place if loaded via UEFI arch/arm/boot/compressed/head.S | 84 +++++++------------- arch/arm/boot/compressed/vmlinux.lds.S | 5 ++ drivers/firmware/efi/libstub/arm32-stub.c | 41 ++-------- 3 files changed, 38 insertions(+), 92 deletions(-) -- 2.17.1
