android_kernel_motorola_sm6225/arch/x86/vdso
Roland McGrath c65916fe35 x86: vdso linker script cleanup
I can't see the reason ".  = VDSO_PRELINK + 0x900;" was ever there in
the linker script for the x86_64 vDSO.  I can't find anything that
depends on this magic offset, or that should care at all about the
particular location of of the .data section (all from vvar.c) in the
vDSO image.  If it is really desireable to place .data at 0x900, then it
should be after all the other sections so they fill in the space up to
0x900.

This removes the 0x900 magic and cleans up the output sections generally
in the vDSO linker script.  This saves a few hundred bytes in the size
of the vDSO file, bringing it back well under 4kb total so that its vma
only needs one page.

Signed-off-by: Roland McGrath <roland@redhat.com>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2007-10-17 20:17:06 +02:00
..
.gitignore x86_64: move vdso 2007-10-11 11:17:10 +02:00
Makefile x86: Install unstripped copy of 64bit vdso to disk 2007-10-17 20:15:20 +02:00
vclock_gettime.c x86_64: move vdso 2007-10-11 11:17:10 +02:00
vdso-note.S x86_64: move vdso 2007-10-11 11:17:10 +02:00
vdso-start.S x86_64: move vdso 2007-10-11 11:17:10 +02:00
vdso.lds.S x86: vdso linker script cleanup 2007-10-17 20:17:06 +02:00
vdso.S x86_64: move vdso 2007-10-11 11:17:10 +02:00
vextern.h x86_64: move vdso 2007-10-11 11:17:10 +02:00
vgetcpu.c x86_64: move vdso 2007-10-11 11:17:10 +02:00
vma.c x86_64: move vdso 2007-10-11 11:17:10 +02:00
voffset.h x86_64: move vdso 2007-10-11 11:17:10 +02:00
vvar.c x86: vdso put vars in rodata 2007-10-17 20:16:43 +02:00