From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: Olaf Hering <olaf@aepfle.de>, Arnd Bergmann <arnd@arndb.de>,
Akinobu Mita <mita@fixstars.com>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
cbe-oss-dev@ozlabs.org
Subject: Re: [patch 3/3] cell: prevent alignment interrupt on local store
Date: Thu, 12 Apr 2007 18:48:11 +1000 [thread overview]
Message-ID: <1176367692.5764.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20070412083135.GA3104@iram.es>
On Thu, 2007-04-12 at 10:31 +0200, Gabriel Paubert wrote:
> On Thu, Apr 12, 2007 at 04:38:10PM +1000, Benjamin Herrenschmidt wrote:
> > On Thu, 2007-04-12 at 08:33 +0200, Olaf Hering wrote:
> > > On Thu, Apr 12, Benjamin Herrenschmidt wrote:
> > >
> > > > Gets altivec and stops working on POWER5 ? no deal :-)
> > >
> > > If there is a significant performance gain (not only 9%) and if
> > > -mcpu=$cell does not generate instructions that wont work on other
> > > altivec capable cpus and if rpm gets a target ppcaltivec.rpm (or
> > > similar), as separate binary tree can be done.
> >
> > -mcpu=cell can possibly generate things that won't run on 970 and 74xx.
> > There are some new altivec instructions among others...
>
> Any pointer to a document describing the differences?
I'm not sure where this is documented. There are a few new ops for
doing load/save of partial vectors (to help handle edge cases),
there are some more precise implementation of some fp osp (though
that should be backward compatible), and maybe a few other things.
I think most public cell docs can be found at
http://www-306.ibm.com/chips/techlib/techlib.nsf/products/Cell_Broadband_Engine
Though I have no idea where those specifics are described.
Cheers,
Ben.
next prev parent reply other threads:[~2007-04-12 8:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 11:15 [patch 3/3] cell: prevent alignment interrupt on local store Akinobu Mita
2007-04-10 12:52 ` Segher Boessenkool
2007-04-11 3:06 ` Akinobu Mita
2007-04-10 21:22 ` Benjamin Herrenschmidt
2007-04-11 2:56 ` Akinobu Mita
2007-04-11 3:30 ` Benjamin Herrenschmidt
2007-04-11 21:03 ` Segher Boessenkool
2007-04-12 4:23 ` Olaf Hering
2007-04-12 5:26 ` Benjamin Herrenschmidt
2007-04-12 6:33 ` Olaf Hering
2007-04-12 6:38 ` Benjamin Herrenschmidt
2007-04-12 8:31 ` Gabriel Paubert
2007-04-12 8:48 ` Benjamin Herrenschmidt [this message]
2007-04-12 6:50 ` Segher Boessenkool
2007-04-12 6:57 ` [Cbe-oss-dev] " Michael Ellerman
2007-04-12 7:07 ` Segher Boessenkool
2007-04-12 18:43 ` Arnd Bergmann
2007-04-12 18:55 ` Arnd Bergmann
2007-04-12 19:57 ` Segher Boessenkool
2007-04-12 19:52 ` Segher Boessenkool
2007-04-12 13:01 ` [RFC, PATCH] selection of CPU optimization Arnd Bergmann
2007-04-12 16:45 ` Kumar Gala
2007-04-12 17:26 ` [Cbe-oss-dev] " Arnd Bergmann
2007-04-12 18:17 ` Kumar Gala
2007-04-12 19:25 ` Arnd Bergmann
2007-04-12 20:04 ` Olof Johansson
2007-04-12 20:01 ` Segher Boessenkool
2007-04-12 20:22 ` Olof Johansson
2007-04-12 20:22 ` Segher Boessenkool
2007-04-12 19:50 ` Segher Boessenkool
2007-04-13 0:10 ` Arnd Bergmann
2007-04-13 2:03 ` Olof Johansson
2007-04-13 18:43 ` Segher Boessenkool
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=1176367692.5764.7.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mita@fixstars.com \
--cc=olaf@aepfle.de \
--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 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).