Re: [PATCH] i386 vsyscall DSO implementation

[Jeff Garzik <jgarzik@pobox.com>]

> Two DSOs are built (a int $0x80 one and a sysenter one), using normal
> assembly code and ld -shared with a special linker script.  Both images
> (stripped ELF .so files) are embedded in __initdata space; sysenter_setup
> copies one or the other whole image into the vsyscall page.  Each image is
> a little under 2k (1884 and 1924) now, and could be trimmed a little bit
> with some specialized ELF stripping that ld and strip don't do.  Adding
> additional entry points should not have much additional overhead beyond the
> code itself and the string size of new symbol names.

We already embed a cpio archive into __initdata space.  What about 
putting the images in there, and either copying the data out of 
initramfs, or, directly referencing the pages that store each image?

	Jeff