From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: Olof Johansson <olof@lixom.net>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
cbe-oss-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [Cbe-oss-dev] Cell and new CPU feature bits
Date: Fri, 26 May 2006 16:19:53 +1000 [thread overview]
Message-ID: <1148624394.8089.90.camel@localhost.localdomain> (raw)
In-Reply-To: <11D4E003-85A4-48A0-9654-BEAE5600B89C@physics.uc.edu>
> > I'm assuming you mean the instructions described under "AltiVec Memory
> > Bandwidth Management" in secion 5.2 of the Altivec PEM -- dst, dstt,
> > dstst, dss and dssall?
>
> They are nops on the Cell though. They are also microcoded on the 970.
It's still useful to have a way to inform userland of their absence (or
inefficency).
> > If you're referring to the extended dcbt that includes streaming hints
> > (as documented in the 64-bit PEM, but not in PPC book2 2.02), then a
> > separate bit is likely needed -- obviously at least 970 seems to
> > implement them.
>
> Yes they are implemented on the 970.
next prev parent reply other threads:[~2006-05-26 6:19 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 [this message]
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
2006-05-19 10:11 ` [Cbe-oss-dev] " 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=1148624394.8089.90.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=pinskia@physics.uc.edu \
/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).