[PATCH/RFT 0/13] x86: unify vmlinux.lds
From: Sam Ravnborg
Date: Wed Apr 29 2009 - 03:33:22 EST
Following patchset is on top of the x86/kbuild branch of tip.
It unifies vmlinux.lds so we end up with a single file.
The patchset has been build tested on 32bit and 64 bit but has
not been boot tested. (Lacking time/resources atm).
The steps were made minimal to make it simpler to track regressions
using bisect (if any) and to make review easier.
The unified vmlinux.lds shows some questionable differences
between 32 bit and 64 bit.
o 64 bit uses PHDRS more extensively than 32 bit. Could they be the same?
o _stext does not cover all text for 32 bit - a bug? For 64b bit it does.
It is only the .code16 wakeup stuff that is not covered but anyway.
o _edata covers much more on 32 bit
o The nosave stuff differs (but that is due to the PHDRS stuff anyway)
o Different alignmnet requirements in several spots
o All the stuff added to support relocable kernels
Please test/review.
This patchset will conflict with Tim's work but the conflicts should
be simple to fix. Lets tackle that later.
Sam
arch/x86/kernel/head_32.S | 7 -
arch/x86/kernel/vmlinux.lds.S | 421 +++++++++++++++++++++++++++++++++++++-
arch/x86/kernel/vmlinux_32.lds.S | 229 ---------------------
arch/x86/kernel/vmlinux_64.lds.S | 336 ------------------------------
4 files changed, 419 insertions(+), 574 deletions(-)
Sam Ravnborg (13):
x86: beautify vmlinux_32.lds.S
x86, vmlinux.lds: unify header/footer
x86, vmlinux.lds: unify PHDRS
x86, vmlinux.lds: unify start/end of SECTIONS
x86, vmlinux.lds: unify .text output sections
x86, vmlinux.lds: unify exceptiontable
x86, vmlinux.lds: unify data output sections
x86, vmlinux.lds: move vsyscall output sections
x86, vmlinux.lds: unify first part of initdata
x86, vmlinux.lds: unify parainstructions
x86, vmlinux.lds: unify .exit.* and .init.ramfs
x86, vmlinux.lds: unify percpu
x86, vmlinux.lds: unify remaining parts
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/