From: Roland McGrath <roland@redhat.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, Nathan Lynch <ntl@pobox.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/2] elf loader support for auxvec base platform string
Date: Sun, 6 Jul 2008 23:18:11 -0700 (PDT) [thread overview]
Message-ID: <20080707061811.19989154246@magilla.localdomain> (raw)
In-Reply-To: Benjamin Herrenschmidt's message of Monday, 7 July 2008 15:48:13 +1000 <1215409693.8970.79.camel@pasglop>
> Well, we use strings to represent the platforms already (ie, the actual
> CPU microarchitecture). Fitting those into bits would be annoying, it
Then use dsocaps.
> makes sense to have AT_BASE_PLATFORM to be the "base" variant of
> AT_PLATFORM.
I understand why you think so. But let's not be too abstract. The
purpose of the addition is to drive ld.so's selection of libraries, yes?
AT_PLATFORM is a lousy model. Handling it is clunky in glibc, because
we have to compare against all the known strings to turn it back into a
bit for the ld.so.cache bitmasks. We're not going to do the same for
AT_BASE_PLATFORM too, because it just sucks.
Using dsocaps gives you the best of both worlds. You can freely choose
new strings in the kernel without the ld.so code having to know about
them (which is not true of AT_PLATFORM, but may be true of how you are
thinking about "strings are nice"). You do have to map all the
possibilities that a single kernel build can produce into distinct bits.
But, there are 32 unallocated bits to start with. Moreover, those bit
assignments are not part of any permanent ABI like bits in AT_* values.
They just have to match up between this kernel build and the ld.conf.d
file installed along with it--kernel hackers and kernel packagers have
to coordinate, not kernel hackers and userland hackers.
Thanks,
Roland
next prev parent reply other threads:[~2008-07-07 6:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 23:41 [PATCH 1/2] elf loader support for auxvec base platform string Nathan Lynch
2008-07-04 2:19 ` Roland McGrath
2008-07-07 5:48 ` Benjamin Herrenschmidt
2008-07-07 6:18 ` Roland McGrath [this message]
2008-07-07 6:23 ` Benjamin Herrenschmidt
2008-07-07 6:35 ` Roland McGrath
2008-07-07 6:48 ` Benjamin Herrenschmidt
2008-07-07 7:49 ` Andreas Schwab
2008-07-07 9:31 ` Roland McGrath
2008-07-07 10:01 ` Andreas Schwab
2008-07-07 22:56 ` Benjamin Herrenschmidt
2008-07-08 0:31 ` Roland McGrath
2008-07-08 0:48 ` Benjamin Herrenschmidt
2008-07-08 18:35 ` Steven Munroe
2008-07-07 16:16 ` Nathan Lynch
2008-07-07 22:17 ` Nathan Lynch
2008-07-07 23:00 ` Benjamin Herrenschmidt
2008-07-04 2:35 ` Mikael Pettersson
2008-07-07 15:55 ` Nathan Lynch
-- strict thread matches above, loose matches on Subject: below --
2008-07-07 15:14 Steven Munroe
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=20080707061811.19989154246@magilla.localdomain \
--to=roland@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--cc=paulus@samba.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