From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>,
mahesh@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc: Export PIR data through sysfs
Date: Fri, 11 Nov 2011 10:17:55 +0530 [thread overview]
Message-ID: <20111111044755.GA19107@in.ibm.com> (raw)
In-Reply-To: <1320985094.21206.35.camel@pasglop>
On Fri, Nov 11, 2011 at 03:18:14PM +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2011-11-10 at 14:18 +0530, Ananth N Mavinakayanahalli wrote:
>
> >
> > From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
> >
> > The Processor Identification Register (PIR) on some powerpc platforms
> > provides information to decode the processor identification tag.
> > Decoding this information is platform specific.
> >
> > We currently need this information for POWERx processors and hence
> > follows a similar model as adopted for the other POWERx specific
> > features.
>
> At this rate we're going to end up with no bits left for CPU features
> way too quickly... Especially for something we only care about once at
> boot time.
>
> Wouldn't CPU_FTR_PPCAS_ARCH_V2 be a good enough test ?
/me checks Cell manuals... yes, that test would be good enough. I will
cook up a patch to use this.
> Can you tell us a bit more about the real use for that feature ? I still
> don't see what's the point of getting the underlying HW ID.
This is a requirement from the hardware system test folks for use with
their core, node and thread tests.
Ananth
next prev parent reply other threads:[~2011-11-11 4:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 4:47 [PATCH] powerpc: Export PIR data through sysfs Ananth N Mavinakayanahalli
2011-11-07 17:18 ` Scott Wood
2011-11-08 6:58 ` Ananth N Mavinakayanahalli
2011-11-08 16:59 ` Scott Wood
2011-11-09 4:41 ` Ananth N Mavinakayanahalli
2011-11-09 15:48 ` Scott Wood
2011-11-10 8:48 ` Ananth N Mavinakayanahalli
2011-11-11 4:18 ` Benjamin Herrenschmidt
2011-11-11 4:47 ` Ananth N Mavinakayanahalli [this message]
2011-11-11 5:58 ` [PATCH V2] " Ananth N Mavinakayanahalli
2011-11-09 6:51 ` [PATCH] " Michael Ellerman
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=20111111044755.GA19107@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=scottwood@freescale.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).