Messages in this thread | | | Date | Thu, 24 Apr 2003 21:49:33 -0400 | From | Jeff Garzik <> | Subject | Re: [PATCH] i386 vsyscall DSO implementation |
| |
> 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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |