From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Michael Neuling <michael.neuling@au1.ibm.com>,
Michael R Meissner <mrmeissn@us.ibm.com>,
sjmunroe@us.ibm.com, bergner@us.ibm.com,
Ryan Arnold <ryanarn@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] arch/powerpc: advertise ISA2.07, HTM, DSCR, EBB and ISEL bits in HWCAP2
Date: Fri, 3 May 2013 16:40:19 -0700 [thread overview]
Message-ID: <20130503234019.GE8561@linux.vnet.ibm.com> (raw)
In-Reply-To: <1367623431.4389.132.camel@pasglop>
On 04.05.2013 [09:23:51 +1000], Benjamin Herrenschmidt wrote:
> On Fri, 2013-05-03 at 16:19 -0700, Nishanth Aravamudan wrote:
> > +/* in AT_HWCAP2 */
> > +#define PPC_FEATURE2_ARCH_2_07 0x80000000
> > +#define PPC_FEATURE2_HTM 0x40000000
> > +#define PPC_FEATURE2_DSCR 0x20000000
> > +#define PPC_FEATURE2_EBB 0x10000000
> > +#define PPC_FEATURE2_ISEL 0x08000000
>
> Should we "adjust" (ie filter out) some of these based
> on CONFIG_ options (such as transactional memory enabled,
> EBB supported by the hypervisor, etc...) ?
Err, yeah, that seems reasonable :) However, it seems like glibc uses
these values rather directly so it knows what bits to check for each
feature. Therefore, it seems like it would be better to do the
ifdeffery/checking in the user in cputable.c, but that seems like it
could get quite complicated.
Would it be ok (I guess I'm asking Ryan & co. here) to have an #ifdef in
the definition that may or may not mean the bit is set in the aux
vector, but the bit, if set, would always be the same bit?
-Nish
next prev parent reply other threads:[~2013-05-03 23:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 23:19 [PATCH] arch/powerpc: advertise ISA2.07, HTM, DSCR, EBB and ISEL bits in HWCAP2 Nishanth Aravamudan
2013-05-03 23:23 ` Benjamin Herrenschmidt
2013-05-03 23:40 ` Nishanth Aravamudan [this message]
2013-05-06 14:38 ` Ryan Arnold
2013-05-06 21:37 ` Benjamin Herrenschmidt
2013-05-07 15:11 ` Ryan Arnold
2013-05-07 20:33 ` Nishanth Aravamudan
2013-05-07 20:49 ` Benjamin Herrenschmidt
2013-05-07 21:11 ` Nishanth Aravamudan
2013-05-03 23:26 ` Michael R Meissner
2013-05-04 21:42 ` Segher Boessenkool
2013-05-04 0:04 ` Michael Neuling
2013-05-04 0:47 ` [PATCH v2 1/4] powerpc/cputable: reserve bits in HWCAP2 for new features Nishanth Aravamudan
2013-05-04 0:48 ` [PATCH v2 2/4] powerpc/cputable: advertise DSCR support on P7/P7+ Nishanth Aravamudan
2013-05-04 0:49 ` [PATCH v2 3/4] powerpc/cputable: advertise ISEL support on appropriate embedded processors Nishanth Aravamudan
2013-05-04 0:49 ` [PATCH v2 4/4] powerpc/cputable: advertise support for ISEL/HTM/DSCR/TAR on POWER8 Nishanth Aravamudan
2013-05-05 2:01 ` [PATCH v3 3/4] powerpc/cputable: advertise ISEL support on appropriate embedded processors Nishanth Aravamudan
2013-05-20 15:04 ` [PATCH v2 2/4] powerpc/cputable: advertise DSCR support on P7/P7+ Will Schmidt
2013-05-20 23:41 ` Michael Neuling
2013-05-06 19:07 ` [PATCH v2 1/4] powerpc/cputable: reserve bits in HWCAP2 for new features Ryan Arnold
2013-05-06 21:41 ` Benjamin Herrenschmidt
2013-05-07 15:07 ` Ryan Arnold
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=20130503234019.GE8561@linux.vnet.ibm.com \
--to=nacc@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bergner@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael.neuling@au1.ibm.com \
--cc=mrmeissn@us.ibm.com \
--cc=ryanarn@us.ibm.com \
--cc=sjmunroe@us.ibm.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).