[PATCH 3/3] efi: enforce usable memory range after reserving regions
Frank van der Linden
fllinden at amazon.com
Mon Jan 10 13:08:09 PST 2022
The usable memory range may be restricted through parameters that
did not come from EFI, like the FDT "linux,usable-memory-range"
property.
Enforce this range after the EFI memory map regions have been
processed.
Signed-off-by: Frank van der Linden <fllinden at amazon.com>
---
drivers/firmware/efi/efi-init.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/firmware/efi/efi-init.c b/drivers/firmware/efi/efi-init.c
index b19ce1a83f91..280e9178c7df 100644
--- a/drivers/firmware/efi/efi-init.c
+++ b/drivers/firmware/efi/efi-init.c
@@ -204,6 +204,13 @@ static __init void reserve_regions(void)
memblock_reserve(paddr, size);
}
}
+
+ /*
+ * Done, filter !nomap memory we just added so that the
+ * usable range is enforced. This is normally only set
+ * for crash kernels on some architectures.
+ */
+ memblock_enforce_usable_range();
}
void __init efi_init(void)
--
2.32.0
More information about the kexec
mailing list