From: Linn Crosetto <linn@hp.com>
To: matt.fleming@intel.com, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, yinghai@kernel.org,
penberg@kernel.org, jacob.shin@amd.com,
linux-efi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Linn Crosetto <linn@hp.com>
Subject: [RFC PATCH 0/4] EFI boot stub memory map fix
Date: Mon, 19 Aug 2013 14:00:15 -0600 [thread overview]
Message-ID: <1376942419-5684-1-git-send-email-linn@hp.com> (raw)
I realize the EFI stub for ARM patches are in flight,
https://lkml.org/lkml/2013/8/9/554
and overlap with some of the files but I wanted to send these out for comment.
This series fixes a problem with EFI memory maps larger than 128 entries when
booting using the EFI boot stub, which results in overflowing the e820_map in
boot_params and an eventual halt when checking the map size in
sanitize_e820_map().
The fix implemented is to add the EFI memory map from setup_arch() via a
memory_setup hook.
Two options were considered:
1. Use the SETUP_E820_EXT setup_data type to add the extra entries.
2. Create a memory_setup function to be enabled when the EFI memory map is
needed.
Option 2 appeared to be the cleaner solution, reducing duplication with
existing code, given a reasonable mechanism for determining when to
replace the default memory_setup function.
Linn Crosetto (4):
efi: Decouple efi_memmap_init() and do_add_efi_memmap()
efi: Add memory_setup function efi_memory_setup()
efi: Add efi_memmap_needed()
x86: Fix EFI boot stub for large memory maps
arch/x86/boot/compressed/eboot.c | 64 ++--------------------------------------
arch/x86/kernel/setup.c | 3 ++
arch/x86/platform/efi/efi.c | 51 +++++++++++++++++++++++---------
include/linux/efi.h | 2 ++
4 files changed, 45 insertions(+), 75 deletions(-)
--
1.7.11.3
next reply other threads:[~2013-08-19 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 20:00 Linn Crosetto [this message]
2013-08-19 20:00 ` [RFC PATCH 1/4] efi: Decouple efi_memmap_init() and do_add_efi_memmap() Linn Crosetto
2013-08-19 20:00 ` [RFC PATCH 2/4] efi: Add memory_setup function efi_memory_setup() Linn Crosetto
2013-08-19 20:00 ` [RFC PATCH 3/4] efi: Add efi_memmap_needed() Linn Crosetto
2013-08-19 20:00 ` [RFC PATCH 4/4] x86: Fix EFI boot stub for large memory maps Linn Crosetto
2013-08-19 20:06 ` [RFC PATCH 0/4] EFI boot stub memory map fix H. Peter Anvin
2013-08-19 20:47 ` Yinghai Lu
2013-08-19 21:09 ` Linn Crosetto
2013-08-19 21:39 ` Yinghai Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1376942419-5684-1-git-send-email-linn@hp.com \
--to=linn@hp.com \
--cc=hpa@zytor.com \
--cc=jacob.shin@amd.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome