Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <Matthew.Wilcox@genedata.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] binfmt_som
Date: Sun, 13 Jun 1999 03:52:54 +0200	[thread overview]
Message-ID: <19990613035254.D31472@mencheca.ch.genedata.com> (raw)


I plunged further into the binfmt_* files today and have a fair idea what needs to be done next.  One passage is slightly troubling me (page 6-126 of the
runtime arch document),

``exec_dsize
This field specifies the size in bytes of the initialised data (does
not have to be a multiple of 4k).  The actual size of the data section
in the file must be a multiple of 4k and can be padded with zeroes to
make it a multiple of 4k.''

Does this mean in the case where exec_dsize is not a multiple of 4k, it
MUST be padded with zeroes, or merely might be padded with zeroes?  If the
former, I don't need to zero them myself in the loader which would be nice.

Also, where does the bss section start?  Is it immediately after the
initialised data or at the next page boundary after it?

binfmt_som is going to be the cleanest binfmt in the kernel when I'm
finished with it :-)  [and then I'm going to clean up the others.]

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

             reply	other threads:[~1999-06-13  1:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-13  1:52 Matthew Wilcox [this message]
1999-06-13  6:40 ` [parisc-linux] binfmt_som Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1999-06-03 17:57 Matthew Wilcox
1999-05-30 23:09 Matthew Wilcox
1999-05-31  0:11 ` Mark Klein

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=19990613035254.D31472@mencheca.ch.genedata.com \
    --to=matthew.wilcox@genedata.com \
    --cc=parisc-linux@thepuffingroup.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