Re: [PATCH 0/3] Early use of boot service memory

["H. Peter Anvin" <hpa@zytor.com>]

The problem with the crashkernel is that it by default has to sit very low in memory because the tools don't know if the crashkernel is me enough to sit anywhere.  That is the real fix.

Jerry Hoemann <jerry.hoemann@hp.com> wrote:
>Some platform have firmware that violates UEFI spec and access boot
>service
>code or data segments after the system has called Exit Boot Services.
>The call to efi_reserve_boot_services in setup_arch is a work around to
>avoid using boot service memory until after the kernel has done
>Set Virtual Map.
>
>However, this reservation fragments memory which can cause
>large allocations early in boot (e.g. crash kernel) to fail.
>
>This patch set extends the add_efi_memmap with an optional
>argument to specify that firmware "correctly" doesn't resuse
>boot services memory after Exit Boot Services.
>
>With this information, setup_arch avoids calling
>efi_reserve_boot_services and fragmenting memory.
>
>
>Jerry Hoemann (3):
>  efi: Early use of boot service memory
>  x86: avoid efi_reserve_boot_services
>  x86, efi: Early use of boot service memory
>
> Documentation/kernel-parameters.txt |  8 ++++++++
> arch/x86/kernel/setup.c             |  2 +-
> arch/x86/platform/efi/efi.c         | 13 +++++++++++--
> include/linux/efi.h                 |  1 +
> 4 files changed, 21 insertions(+), 3 deletions(-)

-- 
Sent from my mobile phone.  Please pardon brevity and lack of formatting.