From: tip-bot for Matt Fleming <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
dyoung@redhat.com, tglx@linutronix.de, vgoyal@redhat.com,
matt.fleming@intel.com
Subject: [tip:x86/urgent] x86/boot: EFI_MIXED should not prohibit loading above 4G
Date: Sat, 7 Jun 2014 09:33:36 -0700 [thread overview]
Message-ID: <tip-745c51673e289acf4d9ffc2835524de73ef923fd@git.kernel.org> (raw)
In-Reply-To: <1402140380-15377-1-git-send-email-matt@console-pimps.org>
Commit-ID: 745c51673e289acf4d9ffc2835524de73ef923fd
Gitweb: http://git.kernel.org/tip/745c51673e289acf4d9ffc2835524de73ef923fd
Author: Matt Fleming <matt.fleming@intel.com>
AuthorDate: Sat, 7 Jun 2014 12:26:20 +0100
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Sat, 7 Jun 2014 09:31:00 -0700
x86/boot: EFI_MIXED should not prohibit loading above 4G
commit 7d453eee36ae ("x86/efi: Wire up CONFIG_EFI_MIXED") introduced a
regression for the functionality to load kernels above 4G. The relevant
(incorrect) reasoning behind this change can be seen in the commit
message,
"The xloadflags field in the bzImage header is also updated to reflect
that the kernel supports both entry points by setting both of
XLF_EFI_HANDOVER_32 and XLF_EFI_HANDOVER_64 when CONFIG_EFI_MIXED=y.
XLF_CAN_BE_LOADED_ABOVE_4G is disabled so that the kernel text is
guaranteed to be addressable with 32-bits."
This is obviously bogus since 32-bit EFI loaders will never place the
kernel above the 4G mark. So this restriction is entirely unnecessary.
But things are worse than that - since we want to encourage people to
always compile with CONFIG_EFI_MIXED=y so that their kernels work out of
the box for both 32-bit and 64-bit firmware, commit 7d453eee36ae
effectively disables XLF_CAN_BE_LOADED_ABOVE_4G completely.
Remove the overzealous and superfluous restriction and restore the
XLF_CAN_BE_LOADED_ABOVE_4G functionality.
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Dave Young <dyoung@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
Link: http://lkml.kernel.org/r/1402140380-15377-1-git-send-email-matt@console-pimps.org
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
| 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--git a/arch/x86/boot/header.S b/arch/x86/boot/header.S
index 0ca9a5c..84c2234 100644
--- a/arch/x86/boot/header.S
+++ b/arch/x86/boot/header.S
@@ -375,8 +375,7 @@ xloadflags:
# define XLF0 0
#endif
-#if defined(CONFIG_RELOCATABLE) && defined(CONFIG_X86_64) && \
- !defined(CONFIG_EFI_MIXED)
+#if defined(CONFIG_RELOCATABLE) && defined(CONFIG_X86_64)
/* kernel/boot_param/ramdisk could be loaded above 4g */
# define XLF1 XLF_CAN_BE_LOADED_ABOVE_4G
#else
next parent reply other threads:[~2014-06-07 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1402140380-15377-1-git-send-email-matt@console-pimps.org>
2014-06-07 16:33 ` tip-bot for Matt Fleming [this message]
2014-06-09 12:54 ` [PATCH] x86/boot: EFI_MIXED should not prohibit loading above 4G Vivek Goyal
2014-06-09 13:18 ` Matt Fleming
2014-06-09 14:15 ` Vivek Goyal
2014-06-09 14:25 ` Matt Fleming
2014-06-09 14:32 ` Vivek Goyal
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=tip-745c51673e289acf4d9ffc2835524de73ef923fd@git.kernel.org \
--to=tipbot@zytor.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
/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