From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Page-aligned executables (Was re: [9fans] Non-stack-based calling conventions)
Date: Mon, 18 Feb 2008 11:53:32 -0500 [thread overview]
Message-ID: <7871fcf50802180853v7473d507w991517014e3cb4bb@mail.gmail.com> (raw)
On Feb 18, 2008 3:38 AM, Anant Narayanan <anant@kix.in> wrote:
> Just as an observation (may not be related to the thread), all the
> executable file formats that Linux currently supports, have page-
> aligned sections in the file! (Now I know why hexdump always shows me
> a bunch of zeros in-between).
>
> That means, all the loader really does is mmap the sections into the
> right memory locations. What next, maybe also put in the BSS in the
> file so you wouldn't have to allocate that either ;)
Ron mentioned that tidbit in his IWP9 talk about booting Plan 9 under
lguest. Lguest (or was it another virtualizer?) uses mmap so it can
load any arbitrary number of client kernels; 9l-produced ELF files
break that model.
> Hence, writing the loader for Plan 9's a.out proved to be a challenge.
>
> I ended up writing a user-space program that padded out the required
> gap between TEXT and DATA before asking the kernel to execute it.
> Suboptimal, but it works.
>
> If anyone has any ideas as to how I can improve the situation, i'll be
> grateful.
What's the context that you're building this loader for?
--Joel
next reply other threads:[~2008-02-18 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 16:53 Joel C. Salomon [this message]
2008-02-18 17:10 ` ron minnich
2008-02-18 18:06 ` Joel C. Salomon
2008-02-18 18:12 ` ron minnich
2008-02-18 18:20 ` Joel C. Salomon
2008-02-18 18:51 ` ron minnich
2008-02-18 19:24 ` Anant Narayanan
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=7871fcf50802180853v7473d507w991517014e3cb4bb@mail.gmail.com \
--to=joelcsalomon@gmail.com \
--cc=9fans@cse.psu.edu \
/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).