All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marvin <marvin24@gmx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: [RFC] [0/5] tuning options for PPC64
Date: Wed, 23 Jul 2008 22:16:31 +0200	[thread overview]
Message-ID: <200807232216.31610.marvin24@gmx.de> (raw)
In-Reply-To: <200807210902.48150.marvin24@gmx.de>


Hi,

and thanks for the feedback. To make it short, the conclusions I draw from 
that are:

	- let the cpu type be choosen optionaly
	- both target cpu and tuning cpu should be selectable
	- if one cpu gets choosen, it should select some feature flag, mcpu and mtune 
option automatically in Kconfig.cputypes
	- if none gets choosen, all features will be selected (is this save?)

I found these ppc64 cpu specific candidates for CONFIG_FEATURE-X:

Altivec (G4, G5, POWER6+7, PA6T)
BAT64 aka POWER3 (Power3)
FPU (all)
Std_MMU (all)
Virt_CPU_Accounting (all, except PA6T?)
VSX (power7)

There are probably some more features present, which are currently enabled by 
some ifdefs for PPC64 and POWER4 (e.g. powermac/feature.c). I will not touch 
them due to my little knowledge and just keep these symbols.

I guess this will become another long weekend ;-)

Marvin


On Monday 21 July 2008 09:02:47 Marvin wrote:
> Hi,
>
> the following five patches should lay a foundation to more fine-grained
> tuning on PPC64 cpus. They must be applied in order. The motivation are the
> discussions of serveral cpu specific optimizations in the past on this
> list, cleanup of the wired Makefile/CONFIG_POWERx constructs and at least
> the ownership of a PS3.
>
> The patches intoduce CONFIG_TUNE_some_cpu and CONFIG_OPT_EXCLUSIVE, with
> the aim to cover two common cases:
>
> 	- distributions want a common kernel, bootable on all ppc64 machines and
> tune for a certain cpu
>
> 	- high end users don't care about older cpus and want to compile a kernel
> with their favorite mcpu option
>
> I know there is also the possibility of mcpu=x and mtune=y, y>x but this
> can be tackled in the next step (hopefully).
>
> I know this will bring up some conserns, but my initial findings grepping
> the defconfigs show:
>
> 	- CONFIG_POWER3 enables BATS only
> 		it is also used the enable some configs
> 		it is used always in combination with CONFIG_POWER4
>
> 	- CONFIG_POWER4 is always combined with CONFIG_PPC64 and vice versa
> 		all POWER3 || POWER4 || PPC64 can be replaced by PPC64
>
> 	- There seems to be no support for 32-bit kernels on ppc64 machines
>
> I hope for some feedback, so this new scheme (or some other) can be
> included to mainstream kernel.
>
> Greetings
>
> Marvin
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev

      reply	other threads:[~2008-07-23 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21  7:02 [RFC] [0/5] tuning options for PPC64 Marvin
2008-07-23 20:16 ` Marvin [this message]

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=200807232216.31610.marvin24@gmx.de \
    --to=marvin24@gmx.de \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.