diff options
author | Mike Rapoport <rppt@kernel.org> | 2021-12-13 14:27:57 +0300 |
---|---|---|
committer | Borislav Petkov <bp@suse.de> | 2021-12-15 16:07:54 +0300 |
commit | 2f5b3514c33fecad4003ce0f22ca9691492d310b (patch) | |
tree | 7beabbb189463e86224767296b88db90dd1701c5 /arch/x86/kernel/irqinit.c | |
parent | fbe6183998546f8896ee0b620ece86deff5a2fd1 (diff) | |
download | linux-2f5b3514c33fecad4003ce0f22ca9691492d310b.tar.xz |
x86/boot: Move EFI range reservation after cmdline parsing
The memory reservation in arch/x86/platform/efi/efi.c depends on at
least two command line parameters. Put it back later in the boot process
and move efi_memblock_x86_reserve_range() out of early_memory_reserve().
An attempt to fix this was done in
8d48bf8206f7 ("x86/boot: Pull up cmdline preparation and early param parsing")
but that caused other troubles so it got reverted.
The bug this is addressing is:
Dan reports that Anjaneya Chagam can no longer use the efi=nosoftreserve
kernel command line parameter to suppress "soft reservation" behavior.
This is due to the fact that the following call-chain happens at boot:
early_reserve_memory
|-> efi_memblock_x86_reserve_range
|-> efi_fake_memmap_early
which does
if (!efi_soft_reserve_enabled())
return;
and that would have set EFI_MEM_NO_SOFT_RESERVE after having parsed
"nosoftreserve".
However, parse_early_param() gets called *after* it, leading to the boot
cmdline not being taken into account.
See also https://lore.kernel.org/r/e8dd8993c38702ee6dd73b3c11f158617e665607.camel@intel.com
[ bp: Turn into a proper patch. ]
Signed-off-by: Mike Rapoport <rppt@kernel.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lore.kernel.org/r/20211213112757.2612-4-bp@alien8.de
Diffstat (limited to 'arch/x86/kernel/irqinit.c')
0 files changed, 0 insertions, 0 deletions