From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Magnus Damm <damm@opensource.se>
Cc: dan@embeddededge.com, ningerso@ruralcenter.org,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Runtime Altivec detection
Date: 07 Mar 2003 19:06:12 +0100 [thread overview]
Message-ID: <1047060372.12202.46.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <20030307185552.0da9897b.damm@opensource.se>
On Fri, 2003-03-07 at 19:55, Magnus Damm wrote:
> > There's a much better way. The kernel passes down CPU features
> > bits down to userland via ELF AUX tables.
>
> Any pointers where I can find information about that?
Well... I know how the kernel pass them down to glibc, but
I don't know how a userland app can retreive them :)
The actual bitmask is defined in kernel's include/asm/cputable.h,
there are 2 sets of feature bits, one for kernel internal usage
and one passed down to userland.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-07 18:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 16:47 Runtime Altivec detection Nathan Ingersoll
2003-03-07 17:24 ` Dan Malek
2003-03-07 17:35 ` Nathan Ingersoll
2003-03-07 17:37 ` Anton Blanchard
2003-03-07 17:41 ` Benjamin Herrenschmidt
2003-03-07 17:52 ` Nathan Ingersoll
2003-03-07 18:55 ` Magnus Damm
2003-03-07 18:06 ` Benjamin Herrenschmidt [this message]
2003-03-07 18:18 ` Hollis Blanchard
2003-03-07 18:54 ` Magnus Damm
2003-03-07 18:08 ` Nathan Ingersoll
2003-03-07 19:44 ` Magnus Damm
2003-03-07 19:23 ` Nathan Ingersoll
-- strict thread matches above, loose matches on Subject: below --
2003-03-08 2:02 Bill Fink
2003-03-08 2:11 ` Hollis Blanchard
2003-03-08 8:04 ` Bill Fink
2003-03-08 18:21 ` Nathan Ingersoll
2003-03-09 4:01 Albert Cahalan
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=1047060372.12202.46.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=damm@opensource.se \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ningerso@ruralcenter.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;
as well as URLs for NNTP newsgroup(s).