* [PATCH -next] x86: vmlinux.lds.S: explain link error better when PHYSICAL_START is LARGE
@ 2020-12-15 0:02 Randy Dunlap
0 siblings, 0 replies; only message in thread
From: Randy Dunlap @ 2020-12-15 0:02 UTC (permalink / raw)
To: linux-kernel
Cc: Randy Dunlap, x86, Thomas Gleixner, Ingo Molnar, Borislav Petkov,
H. Peter Anvin
On i386, when CONFIG_PHYSICAL_START is very large, it causes a
confusing or misleading linker error message:
ld: kernel image bigger than KERNEL_IMAGE_SIZE
so expand this message to include the possibility that the problem
could be due to CONFIG_PHYSICAL_START.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
---
arch/x86/kernel/vmlinux.lds.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20201214.orig/arch/x86/kernel/vmlinux.lds.S
+++ linux-next-20201214/arch/x86/kernel/vmlinux.lds.S
@@ -458,7 +458,7 @@ SECTIONS
* The ASSERT() sink to . is intentional, for binutils 2.14 compatibility:
*/
. = ASSERT((_end - LOAD_OFFSET <= KERNEL_IMAGE_SIZE),
- "kernel image bigger than KERNEL_IMAGE_SIZE");
+ "kernel image bigger than KERNEL_IMAGE_SIZE or CONFIG_PHYSICAL_START too large");
#ifdef CONFIG_X86_64
/*
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-12-15 0:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-15 0:02 [PATCH -next] x86: vmlinux.lds.S: explain link error better when PHYSICAL_START is LARGE Randy Dunlap
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).