From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: "'Peter Bergner'" <bergner@vnet.ibm.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: Re: TASK_UNMAPPED_BASE
Date: Thu, 5 Feb 2004 18:10:52 +0100 [thread overview]
Message-ID: <002c01c3ec0b$0240ea70$0a01a8c0@LUMENTIS02> (raw)
In-Reply-To: <1075998857.2843.14.camel@otta.rchland.ibm.com>
> On Thu, 2004-02-05 at 02:57, Joakim Tjernlund wrote:
> > Too low, does that mean TASK_UNMAPED_BASE < 0x00100000 will fail
> > with huge bss's as well? Or will it just fail for 0x30000000 =>
> > TASK_UNMAPED_BASE <= 0x10000000?
> >
> > To me it seems like it is a good idea to change(at least in 2.6
> > where the bugs you mentioned has been fixed) TASK_UNMAPED_BASE to
> > 0x00100000(or lower).
>
> The problem with a TASK_UNMAPPED_BASE that was "too low" was referring
> to the bug where we always loaded ld.so at TASK_UNMAPPED_BASE even
> though that adress was in the middle of the bss. Now that has been
> fixed, "too low" isn't a concern anymore.
OK, thanks.
> However, I'm not sure moving the TASK_UNMAPPED_BASE below the text
> section will work. It's used for more than just loading shared libs.
> Anonymous mmap areas and the heap are all located relative to it.
hmm, I have tried several values, for instance anything 0x2000 between
(0x10000000-0x16000) appears to work. (0x10000000-0x15000) don't boot,
but then I am on 2.4, so maybe it's the huge bss bug that bites me.
> > Is there a way I can tell glibc to load it's libs around
> > TASK_UNMAPED_BASE? Currently only ld.so follows TASK_UNMAPED_BASE,
> > the other libs always loads at 0x0fxxxxxx. Glibc/ld.so version is
> > 2.2.3
>
> IIRC, only ppc32 loads it's libs this way. For example, ppc64 loads
> all its libs above TASK_UNMAPPED_BASE.
Well, I am ppc32.
Jocke
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-02-05 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 13:05 TASK_UNMAPPED_BASE Joakim Tjernlund
2004-02-03 15:22 ` TASK_UNMAPPED_BASE Franz Sirl
2004-02-03 16:51 ` TASK_UNMAPPED_BASE Joakim Tjernlund
2004-02-04 14:37 ` TASK_UNMAPPED_BASE Peter Bergner
2004-02-04 14:47 ` TASK_UNMAPPED_BASE Anton Blanchard
2004-02-04 21:58 ` TASK_UNMAPPED_BASE Peter Bergner
2004-02-05 8:57 ` TASK_UNMAPPED_BASE Joakim Tjernlund
2004-02-05 16:34 ` TASK_UNMAPPED_BASE Peter Bergner
2004-02-05 17:06 ` TASK_UNMAPPED_BASE Anton Blanchard
2004-02-06 10:53 ` TASK_UNMAPPED_BASE Joakim Tjernlund
2004-02-05 17:10 ` Joakim Tjernlund [this message]
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='002c01c3ec0b$0240ea70$0a01a8c0@LUMENTIS02' \
--to=joakim.tjernlund@lumentis.se \
--cc=bergner@vnet.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).