aboutsummaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/vmlinux_64.lds.S
diff options
context:
space:
mode:
authorRoland McGrath <roland@redhat.com>2008-04-27 18:45:38 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2008-04-28 13:49:35 -0700
commitd9dedc13851f9cbd568fbc631a17b0be83404957 (patch)
tree4ced6cf6715c0805d1f15fd414b0c97a69fe6b1c /arch/x86/kernel/vmlinux_64.lds.S
parent7f6c69dcf40a227b8c98e5619367269b427164d7 (diff)
downloadkernel_samsung_smdk4412-d9dedc13851f9cbd568fbc631a17b0be83404957.zip
kernel_samsung_smdk4412-d9dedc13851f9cbd568fbc631a17b0be83404957.tar.gz
kernel_samsung_smdk4412-d9dedc13851f9cbd568fbc631a17b0be83404957.tar.bz2
x86_64 vDSO: use initdata
The 64-bit vDSO image is in a special ".vdso" section for no reason I can determine. Furthermore, the location of the vdso_end symbol includes some wrongly-calculated padding space in the image, which is then (correctly) rounded to page size, resulting in an extra page of zeros in the image mapped in to user processes. This changes it to put the vdso.so image into normal initdata as we have always done for the 32-bit vDSO images. The extra padding is gone, so the user VMA is one page instead of two. The image that was already copied around at boot time is now in initdata, so we recover that wasted space after boot. Signed-off-by: Roland McGrath <roland@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/x86/kernel/vmlinux_64.lds.S')
-rw-r--r--arch/x86/kernel/vmlinux_64.lds.S6
1 files changed, 0 insertions, 6 deletions
diff --git a/arch/x86/kernel/vmlinux_64.lds.S b/arch/x86/kernel/vmlinux_64.lds.S
index b7ab3c3..fad3674 100644
--- a/arch/x86/kernel/vmlinux_64.lds.S
+++ b/arch/x86/kernel/vmlinux_64.lds.S
@@ -209,12 +209,6 @@ SECTIONS
EXIT_DATA
}
-/* vdso blob that is mapped into user space */
- vdso_start = . ;
- .vdso : AT(ADDR(.vdso) - LOAD_OFFSET) { *(.vdso) }
- . = ALIGN(PAGE_SIZE);
- vdso_end = .;
-
#ifdef CONFIG_BLK_DEV_INITRD
. = ALIGN(PAGE_SIZE);
__initramfs_start = .;