[Cbe-oss-dev] [RFC, PATCH] selection of CPU optimization

Olof Johansson olof at lixom.net
Fri Apr 13 12:03:09 EST 2007


On Fri, Apr 13, 2007 at 02:10:47AM +0200, Arnd Bergmann wrote:
> On Thursday 12 April 2007, Segher Boessenkool wrote:
> > > What would be the right options to pass on e200 and on
> > > pa6t?
> > 
> > The best thing would be to add GCC -mcpu= options. ?For
> > now, you're probably best of with -mcpu=powerpc and
> > -mcpu=powerpc64 resp., i.e. the "blended models". ?This
> > is a good option for multiplatform kernels too; add -mtune=
> > to optimise for a specific core, but it will *work* on
> > the whole family.
> 
> 970 -> -mcpu=970 >> -mcpu=power4
> cell -> -mcpu=cell >> -mcpu=970
> power5 -> -mcpu=power5 >> -mcpu=power4
> power5+ -> -mcpu=power5+ >> -mcpu=power5
> power6 -> -mcpu=power6 >> -mcpu=power5+
> power6x -> -mcpu=power6x >> -mcpu=power6
> pa6t -> -mcpu=pa6t >> (???)
> 
> So if we select e.g. power6 and cell, it needs to fall back to power4,
> which is the common subset. Selecting both 403 and 405 would result
> in falling back to -mcpu=powerpc, because they don't have any larger
> subset.
> 
> I'm not sure what the right fallback fo pa6t should be. I would guess
> that it's a superset of power6x and 970 when considering the kernel,
> but it's not entirely clear what the fallback should be.

On the kernel side, power6 should be closest. We likely lack some of the
optional features they implemented, but none are used in the kernel.

If we find problems down the road, we'll revise.


-Olof



More information about the cbe-oss-dev mailing list