From: Arnd Bergmann <arnd@arndb.de>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org, pantelis.antoniou@gmail.com,
linuxppc64-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] powerpc: merge include/asm/cputable.h
Date: Sat, 17 Sep 2005 02:36:35 +0200 [thread overview]
Message-ID: <200509170236.35963.> (raw)
In-Reply-To: <17FA692D-4643-4390-AE8A-AEF6F716C5EE@freescale.com>
On Freedag 16 September 2005 23:40, Kumar Gala wrote:
> However, I do have some questions, why introduce new Kconfig options
> for ppc64. It seems overkill to have specific build options for each
> "class" of ppc64. One could make the argument we should go do the
> same thing for classic ppc32. From an embedded point of view I could
> reduce down to the specific cpu I'm using. I really dont think we
> want to start doing this.
Note that the configuration options that my patch introduced are
all autodetected from the existing platform CONFIG_PPC_ symbols, so
they don't give you extra settings that might be messed up.
Having the options makes the enum in cpufeatures.h more readable
imho, but if you want to do a patch without them, I wont complain.
> If we did I would have to say we would have to add Kconfig for 601,
> 603, 604, 750 (740, 750, 755), 7400 (7400/7410), 7450 (744x/745x).
> That's six more Kconfig options
I actually like the idea more flexibility to which CPU optimizations
you get in the kernel. These could be combined with the gcc -mcpu=
argument, if there is a way for Kconfig to deduce the most generic
cpu type that still supports all selected models.
The easiest way to do something like this should be to add more
choices to the existing "Processor Type" submenu instead of having
each one selectable separately.
Something tells me that the platform and CPU type selection will
keep us busy for some time, because they are currently treated very
differently in ppc and ppc64. Please tell me if I understand this
correctly:
In ppc, the user can select one out of 27 platforms and one out of
seven separate sets of CPUs. All platforms except CHRP/PowerMac/PReP
can only ever work with a specific CPU selection, while that one
platform has the choice between 6xx/7xx/74xx/52xx/82xx/83xx, POWER3
and POWER4/970. These connections are currently not documented.
In ppc64, the user has to choose between the legacy iSeries and
the generic platform. Generic means any combination of pSeries,
PowerMac, Cell or Maple. The only CPU selection possibility is
'any cpu' or 'Power4 or better'. In future, we will have at least
a third option 'Book E' (or e700), which is incompatible with the
others. With my patch applied, the kernel would automatically disable
support for CPUs that are not possible with the selected platform
setting.
Arnd <><
next prev parent reply other threads:[~2005-09-17 0:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 21:02 cpu features testing 32 vs 64 bit Becky Bruce
2005-09-08 21:08 ` Pantelis Antoniou
2005-09-08 21:20 ` Kumar Gala
2005-09-08 21:48 ` Dan Malek
2005-09-08 22:02 ` Kumar Gala
2005-09-08 22:20 ` Dan Malek
2005-09-08 22:36 ` Arnd Bergmann
2005-09-09 0:08 ` David Gibson
2005-09-09 4:23 ` [PATCH] powerpc: merge include/asm/cputable.h Arnd Bergmann
2005-09-14 19:11 ` Kumar Gala
2005-09-14 23:58 ` Arnd Bergmann
2005-09-15 17:44 ` Kumar Gala
2005-09-15 22:56 ` Arnd Bergmann
2005-09-16 2:22 ` Kumar Gala
2005-09-16 3:11 ` Arnd Bergmann
2005-09-16 21:40 ` Kumar Gala
2005-09-17 0:36 ` Arnd Bergmann [this message]
2005-09-09 22:19 ` cpu features testing 32 vs 64 bit 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=200509170236.35963. \
--to=arnd@arndb.de \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=pantelis.antoniou@gmail.com \
/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).