1
linux/arch/x86/vdso
Roland McGrath d9dedc1385 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>
2008-04-28 13:49:35 -07:00
..
vdso32
.gitignore
Makefile x86 vDSO: compile with -g, 64-bit 2008-04-19 19:19:55 +02:00
vclock_gettime.c
vdso32-setup.c x86: Centaur Isaiah processor to use sysenter in 64-bit compatibility mode rather than syscall 2008-04-17 17:41:31 +02:00
vdso32.S
vdso-layout.lds.S
vdso-note.S
vdso.lds.S
vdso.S x86_64 vDSO: use initdata 2008-04-28 13:49:35 -07:00
vextern.h
vgetcpu.c
vma.c
vvar.c