From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
cbe-oss-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: Cell and new CPU feature bits
Date: Fri, 26 May 2006 16:22:21 +1000 [thread overview]
Message-ID: <1148624542.8089.94.camel@localhost.localdomain> (raw)
In-Reply-To: <20060519081654.GB22952@iram.es>
On Fri, 2006-05-19 at 10:16 +0200, Gabriel Paubert wrote:
> Is this bug really going to be exposed in the wild or is it
> an early silicon bug that will only bite early-testers?
In the wild.
> > - Additional Altivec instructions (load/store right/left). A new
> > feature bit for these ?
>
> Yes. So IBM was not happy with Altivec instructions to generate
> vsel control words and got their inspiration from MIPS?
No idea ;)
> Is it really important? These instructions become nop on Cell, so their
> impact on performance should be minimal while they may be useful in
> code designed to run on any processor having Altivec.
We can ignore that problem (datastream, I cut too much of the original
message :) I suppose but I'd like to have as much point of views here as
we are tackling kernel ABI issues so we can't change things every five
minutes here.
> I believe that a Cell bit would be useful. After all you need a bit
> that tell you that you have the SPUs and related infrastructure?
We already have microarchitecture and SPUs can be detected via the
device-tree or sysfs. But that dcbt X form also exist on other
processors
> > - Not strictly Cell specific but we currently don't expose the support
> > for optional instructions
> > fres and frsqte (which are supported by Cell)
>
> Should be exposed IMHO. But these instructions have been present
> in a lot of PPC processors AFAIR, they are in my original 603 and
> 604 manuals from 1994 (fsel is also marked as optional and is not
> implemented on the 601, but I'm not sure it's really supported
> anymore). I don't know about Power processors.
So what do you suggest I do ? Add feature bits for them and for fsel
too ?
next prev parent reply other threads:[~2006-05-26 6:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 4:07 Cell and new CPU feature bits Benjamin Herrenschmidt
2006-05-19 5:19 ` Olof Johansson
2006-05-19 5:27 ` [Cbe-oss-dev] " Andrew Pinski
2006-05-19 7:49 ` Segher Boessenkool
2006-05-26 6:19 ` Benjamin Herrenschmidt
2006-05-26 6:19 ` Benjamin Herrenschmidt
2006-05-26 6:43 ` Olof Johansson
2006-05-26 7:33 ` Benjamin Herrenschmidt
2006-05-26 15:16 ` Olof Johansson
2006-05-19 8:16 ` Gabriel Paubert
2006-05-22 19:46 ` [Cbe-oss-dev] " Alex Rosenberg
2006-05-23 21:52 ` Benjamin Herrenschmidt
2006-05-26 6:22 ` Benjamin Herrenschmidt [this message]
2006-05-19 10:11 ` Arnd Bergmann
2006-05-19 16:18 ` Olof Johansson
2006-05-19 22:33 ` Paul Mackerras
2006-05-26 6:22 ` [Cbe-oss-dev] " Benjamin Herrenschmidt
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=1148624542.8089.94.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paubert@iram.es \
--cc=paulus@samba.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 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.