From: Paul Bame <bame@debian.fc.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] _end symbol in parisc linux?
Date: Thu, 11 Nov 1999 08:36:14 -0700 [thread overview]
Message-ID: <199911111536.IAA19092@debian.fc.hp.com> (raw)
In-Reply-To: Your message of "Sat, 06 Nov 1999 13:08:22 MST." <30261.941918902@upchuck>
I'm also worried about why there are data symbols following BSS in
our current palinux kernel...
= Though I'd worry about precisely *why* someone wants the _end symbol; whatever
= they're trying to do there's probably a better way.
Maybe there is a better way. The first reason I want to use _end
(and _edata) is to clear the kernel BSS reliably (which is working
great).
The second reason, which doesn't currently work, is to have a symbol
pointing at the very end of kernel memory, since that is where
free memory will start.
Both these tasks are currently being done at run-time -- in one case
by parsing the SOM header and in another case by guessing about a
parameter passed in by the hpux bootloader -- neither is currently
reliable despite the considerable experimentation and
sweat others have poured into the effort. I want to avoid parsing
the SOM header and guessing about bootloaders in the future. It
would also be great to use an old, reliable, and language-system
independent.
-P
next prev parent reply other threads:[~1999-11-11 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 0:39 [parisc-linux] _end symbol in parisc linux? Paul Bame
1999-11-06 18:26 ` Philipp Rumpf
1999-11-06 20:08 ` Jeffrey A Law
1999-11-11 15:36 ` Paul Bame [this message]
1999-11-11 15:51 ` Jeffrey A Law
1999-11-11 16:14 ` Paul Bame
1999-11-11 17:32 ` Jeffrey A Law
1999-11-11 16:46 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
1999-11-02 19:13 Donald Scobbie
1999-11-08 19:18 Cary Coutant
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=199911111536.IAA19092@debian.fc.hp.com \
--to=bame@debian.fc.hp.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