Re: ondemand as default governor

[Thomas Renninger <trenn@suse.de>]

On Wed, 2007-03-07 at 02:02 -0500, Dave Jones wrote:
> On Wed, Mar 07, 2007 at 01:24:28AM -0500, Len Brown wrote:
>  > On Thursday 01 March 2007 12:41, Thomas Renninger wrote:
>  > > I just read in drivers/cpufreq/Kconfig:
>  > > 
>  > > # Note that it is not currently possible to set the other governors
>  > > (such as ondemand)
>  > > # as the default, since if they fail to initialise, cpufreq will be
>  > > # left in an undefined state.
>  > > 
>  > > Is this a bigger problem to solve?
>  > > Is there already someone working/thinking on/about a solution?
>  > > 
>  > > Allowing this would be convenient...
>  > 
>  > Yes, it would, then we could delete the other governors,
>  > and then delete the concept of multiple governors alltogether.
> 
> It's not feasible unless you have a way of making various
> older CPUs transition faster.  Ondemand on longhaul,powernow-k6,longrun,
> elanfreq, as well as lots of non-x86 implementations is just not
> a feasible option.
> 
> However.. conservative might be.  I'd still like to see conservative
> folded into ondemand sometime, and just be a module param.

I like the several governors concept in general, cpuidle also goes this
way now? I'd just like to see cpufreq working by simply loading the
drivers.
I thought I could just set ondemand as default and things work on most
machines, instead of fixing the setup in rescue, installation, whatever
environment.

Especially ThinkPads tend to run hot quite quickly...

   Thomas