]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
efi: support booting with kexec handover (KHO)
authorEvangelos Petrongonas <epetron@amazon.de>
Thu, 21 Aug 2025 17:59:00 +0000 (17:59 +0000)
committerAndrew Morton <akpm@linux-foundation.org>
Sun, 14 Sep 2025 00:32:57 +0000 (17:32 -0700)
commit5b86af1ded2d90402477dce6d4cf8dfa95cca6ac
treed2d8377eee0a0ae01f014637ec374c9990f13f99
parentd6d5116391857fc78fad9aa42317b36e4ce17b58
efi: support booting with kexec handover (KHO)

When KHO (Kexec HandOver) is enabled, it sets up scratch memory regions
early during device tree scanning.  After kexec, the new kernel
exclusively uses this region for memory allocations during boot up to the
initialization of the page allocator

However, when booting with EFI, EFI's reserve_regions() uses
memblock_remove(0, PHYS_ADDR_MAX) to clear all memory regions before
rebuilding them from EFI data.  This destroys KHO scratch regions and
their flags, thus causing a kernel panic, as there are no scratch memory
regions.

Instead of wholesale removal, iterate through memory regions and only
remove non-KHO ones.  This preserves KHO scratch regions, which are good
known memory, while still allowing EFI to rebuild its memory map.

Link: https://lkml.kernel.org/r/b34da9fd50c89644cd4204136cfa6f5533445c56.1755721529.git.epetron@amazon.de
Signed-off-by: Evangelos Petrongonas <epetron@amazon.de>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Acked-by: Pratyush Yadav <pratyush@kernel.org>
Cc: Alexander Graf <graf@amazon.com>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: Baoquan He <bhe@redhat.com>
Cc: Changyuan Lyu <changyuanl@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
drivers/firmware/efi/efi-init.c