linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: Benjamin, linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Paul Mackerras <paulus@samba.org>,
	Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH 1/2] elf loader support for auxvec base platform string
Date: Mon, 7 Jul 2008 10:55:10 -0500	[thread overview]
Message-ID: <20080707155510.GE9594@localdomain> (raw)
In-Reply-To: <18541.35978.437115.957054@harpo.it.uu.se>

Mikael Pettersson wrote:
> Nathan Lynch writes:
>  > Some IBM POWER-based platforms have the ability to run in a
>  > mode which mostly appears to the OS as a different processor from the
>  > actual hardware.  For example, a Power6 system may appear to be a
>  > Power5+, which makes the AT_PLATFORM value "power5+".
>  > 
>  > However, some applications (virtual machines, optimized libraries) can
>  > benefit from knowledge of the underlying CPU model.  A new aux vector
>  > entry, AT_BASE_PLATFORM, will denote the actual hardware.  For
>  > example, on a Power6 system in Power5+ compatibility mode, AT_PLATFORM
>  > will be "power5+" and AT_BASE_PLATFORM will be "power6".
> 
> Why on earth would you ever want AT_PLATFORM to differ from AT_BASE_PLATFORM?
> In cases that matter you admit that AT_BASE_PLATFORM takes precedence,
> so why involve a fake lame not-quite-the-platform in the first place?
> 
> Workaround for buggy software?

My apologies, I did not explain the motivation well.

The idea is that while AT_PLATFORM indicates the instruction set
supported, AT_BASE_PLATFORM indicates the underlying
microarchitecture.  It's not a matter of buggy software, or of one
value taking precedence over the other.

  reply	other threads:[~2008-07-07 15:55 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
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 [this message]
  -- 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=20080707155510.GE9594@localdomain \
    --to=ntl@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mikpe@it.uu.se \
    --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 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).