[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1384222558-38527-1-git-send-email-jerry.hoemann@hp.com>
Date: Mon, 11 Nov 2013 19:15:55 -0700
From: Jerry Hoemann <jerry.hoemann@...com>
To: rob@...dley.net, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, matt.fleming@...el.com,
yinghai@...nel.org, penberg@...nel.org, akpm@...ux-foundation.org,
linux-doc@...r.kernel.org, linux-efi@...r.kernel.org,
vgoyal@...hat.com
Cc: linux-kernel@...r.kernel.org, jerry.hoemann@...com
Subject: [PATCH 0/3] Early use of boot service memory
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(-)
--
1.7.11.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists