All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Roland McGrath <roland@redhat.com>
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: Mon, 07 Jul 2008 16:23:20 +1000	[thread overview]
Message-ID: <1215411800.8970.91.camel@pasglop> (raw)
In-Reply-To: <20080707061811.19989154246@magilla.localdomain>

On Sun, 2008-07-06 at 23:18 -0700, Roland McGrath wrote:
> 
> 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.

I'm not sure... if ld.conf.d isn't parse of the kernel source tree then
it -will- end in tears...

Ben.

WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Roland McGrath <roland@redhat.com>
Cc: Nathan Lynch <ntl@pobox.com>,
	linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] elf loader support for auxvec base platform string
Date: Mon, 07 Jul 2008 16:23:20 +1000	[thread overview]
Message-ID: <1215411800.8970.91.camel@pasglop> (raw)
In-Reply-To: <20080707061811.19989154246@magilla.localdomain>

On Sun, 2008-07-06 at 23:18 -0700, Roland McGrath wrote:
> 
> 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.

I'm not sure... if ld.conf.d isn't parse of the kernel source tree then
it -will- end in tears...

Ben.



  reply	other threads:[~2008-07-07  6:23 UTC|newest]

Thread overview: 39+ 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-03 23:41 ` Nathan Lynch
2008-07-04  2:19 ` Roland McGrath
2008-07-04  2:19   ` Roland McGrath
2008-07-07  5:48   ` Benjamin Herrenschmidt
2008-07-07  5:48     ` Benjamin Herrenschmidt
2008-07-07  6:18     ` Roland McGrath
2008-07-07  6:18       ` Roland McGrath
2008-07-07  6:23       ` Benjamin Herrenschmidt [this message]
2008-07-07  6:23         ` Benjamin Herrenschmidt
2008-07-07  6:35         ` Roland McGrath
2008-07-07  6:35           ` Roland McGrath
2008-07-07  6:48           ` Benjamin Herrenschmidt
2008-07-07  6:48             ` Benjamin Herrenschmidt
2008-07-07  7:49           ` Andreas Schwab
2008-07-07  7:49             ` Andreas Schwab
2008-07-07  9:31             ` Roland McGrath
2008-07-07  9:31               ` Roland McGrath
2008-07-07 10:01               ` Andreas Schwab
2008-07-07 10:01                 ` Andreas Schwab
2008-07-07 22:56                 ` Benjamin Herrenschmidt
2008-07-07 22:56                   ` Benjamin Herrenschmidt
2008-07-08  0:31                   ` Roland McGrath
2008-07-08  0:31                     ` Roland McGrath
2008-07-08  0:48                     ` Benjamin Herrenschmidt
2008-07-08  0:48                       ` Benjamin Herrenschmidt
2008-07-08 18:35                       ` Steven Munroe
2008-07-08 18:35                         ` Steven Munroe
2008-07-07 16:16       ` Nathan Lynch
2008-07-07 16:16         ` Nathan Lynch
2008-07-07 22:17     ` Nathan Lynch
2008-07-07 22:17       ` Nathan Lynch
2008-07-07 23:00       ` Benjamin Herrenschmidt
2008-07-07 23:00         ` Benjamin Herrenschmidt
2008-07-04  2:35 ` Mikael Pettersson
2008-07-04  2:35   ` Mikael Pettersson
2008-07-07 15:55   ` Nathan Lynch
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=1215411800.8970.91.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ntl@pobox.com \
    --cc=paulus@samba.org \
    --cc=roland@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.