From: Jeff Garzik <jgarzik@pobox.com>
To: Roland McGrath <roland@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, Ulrich Drepper <drepper@redhat.com>
Subject: Re: [PATCH] i386 vsyscall DSO implementation
Date: Thu, 24 Apr 2003 21:49:33 -0400 [thread overview]
Message-ID: <3EA8942D.4050201@pobox.com> (raw)
In-Reply-To: <200304250110.h3P1Aoo02525@magilla.sf.frob.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
next prev parent reply other threads:[~2003-04-25 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 1:10 [PATCH] i386 vsyscall DSO implementation Roland McGrath
2003-04-25 1:49 ` Jeff Garzik [this message]
2003-04-25 2:10 ` Roland McGrath
2003-04-25 16:21 ` David Mosberger
2003-04-25 21:00 ` H. Peter Anvin
2003-04-25 21:17 ` David Mosberger
2003-04-25 21:20 ` H. Peter Anvin
2003-04-25 21:50 ` David Mosberger
2003-04-26 22:06 ` Roland McGrath
2003-04-26 17:15 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EA8942D.4050201@pobox.com \
--to=jgarzik@pobox.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).