From: Arnd Bergmann <arnd@arndb.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [patch 2/9] autoselect optimal -mcpu= flag by platform
Date: Sun, 17 Jun 2007 19:20:10 +0200 [thread overview]
Message-ID: <200706171920.10898.arnd@arndb.de> (raw)
In-Reply-To: <91EBCC0C-48B7-4748-A936-E74CEB7685E0@kernel.crashing.org>
On Sunday 17 June 2007, you wrote:
>
> On Jun 15, 2007, at 7:05 PM, arnd@arndb.de wrote:
>
> > We can choose the -mcpu= gcc flags for compiling the kernel
> > based on the platform that we build for. In case of multiplatform
> > kernels, this chooses a setting for a common subset.
> >
> > When using a platform type that can use different CPUs, a
> > new option CONFIG_PPC_CPU_SELECTION can be enabled to select
> > more specifically which CPUs the kernel will be able to
> > run on.
> >
> > This replaces the CONFIG_POWER4_ONLY option with an much more
> > generic approach.
> >
> > Also, when CONFIG_PPC_CPU_SELECTION is set, it is now possible
> > to select a CPU to tune for by means of the -mtune= option.
> >
> > I tried to be very careful when coding the specific rules into
> > the Kconfig language, but it would be good to have a few
> > people sanity-checking them.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Is there a reason we don't distinguish between 7400/7410 and 74{4,5}
> x? Is it because we dont have any discrete systems with just a 7400
> on it?
No, I just didn't know that there was a difference. I had looked at the
gcc source and found that gcc produces the same instruction for both,
but I didn't bother to look at the optimizations. From all I can
tell, -mcpu=7400 is identical to -mcpu=7450 -mtune=750.
Can you look through the patch again to see which of the platforms
that have a 7400 instead of 7450 type CPUs?
> Also I'd suggest we have the config options be a 1:1 matching for the
> -mcpu/-mtune options in gcc for the following cases:
>
> > + default "-mcpu=750" if CPU_7xx
> > + default "-mcpu=7450" if CPU_74xx
> > + default "-mcpu=860" if PPC_8xx
> > + default "-mcpu=8540" if PPC_85xx
>
> So if in the future we have code scheduling for 8599 or some other
> variant we don't have to go change the Kconfig just add to it.
I'm not sure I understand what you would like to see this, would you
like them to be simply renamed to CPU_750/CPU_7450/CPU_860/CPU_8540
or rather add more options for 740/801/821/823/8548, which are
treated as aliases of the others?
For 74xx, I guess you already convinced me and for 85xx, I'll trust
your word if you think that we will need future flags in the future.
I'm not so sure about 7xx and 8xx though. I could not find any
code in gcc that knows about the difference between the CPUs in
either family, and it doesn't seem like anyone is working on
changing that. Anything I missed there?
Arnd <><
next prev parent reply other threads:[~2007-06-17 17:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070616000511.712667424@arndb.de>
2007-06-16 0:05 ` [patch 1/9] move 82xx/83xx/86xx Kconfig options to platform selection arnd
2007-06-17 14:42 ` Kumar Gala
2007-07-11 15:35 ` Mark A. Greer
2007-07-11 20:33 ` Arnd Bergmann
2007-07-11 21:19 ` Segher Boessenkool
2007-07-11 23:47 ` Mark A. Greer
2007-06-16 0:05 ` [patch 2/9] autoselect optimal -mcpu= flag by platform arnd
2007-06-17 14:29 ` Kumar Gala
2007-06-17 16:11 ` Segher Boessenkool
2007-06-17 17:20 ` Arnd Bergmann [this message]
2007-06-17 17:46 ` Segher Boessenkool
2007-06-29 5:58 ` Paul Mackerras
2007-06-16 0:05 ` [patch 3/9] rename add_bridge to avoid namespace clashes arnd
2007-06-16 0:05 ` [patch 4/9] mpc82xx_ads build fix arnd
2007-06-16 7:37 ` Stephen Rothwell
2007-06-16 9:33 ` [updated PATCH] " Arnd Bergmann
2007-06-16 0:05 ` [patch 5/9] kill isa_{io,mem}_base definitions for !PCI arnd
2007-06-17 14:33 ` Kumar Gala
2007-06-17 15:32 ` Arnd Bergmann
2007-06-16 0:05 ` [patch 6/9] fix building without PCI arnd
2007-06-16 0:05 ` [patch 7/9] disallow building powermac and tsi108 " arnd
2007-06-17 14:35 ` Kumar Gala
2007-06-17 15:32 ` Arnd Bergmann
2007-06-16 0:05 ` [patch 8/9] fix conflicting mpc85xx board headers arnd
2007-06-16 0:05 ` [patch 9/9] enable multiplatform support for embedded boards arnd
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=200706171920.10898.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--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).