[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878x3o5c5h.fsf@saeurebad.de>
Date: Fri, 21 Dec 2007 15:56:58 +0100
From: Johannes Weiner <hannes@...urebad.de>
To: Michael Tokarev <mjt@....msk.ru>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Jones <davej@...emonkey.org.uk>
Subject: Re: 2.6.24-rc5-git7: Reported regressions from 2.6.23
Hi,
Michael Tokarev <mjt@....msk.ru> writes:
> By the way, is there any real need to specify default governor at
> a compile time in the first place? Performance governor (which was
> the only default so far) is a very simple one (not large to consider
> its size effects for embedded systems for example), and switching
> governors at run time is trivial as well. What's the motivation
> behind this new config option?
I think it is just convenient. If you never use the performance
governor, there is no need to compile it. I have no need for an init
script that changes the governor on runtime, too. I just say, use this
and nothing else, ever. Don't know if this convenience is worth the
trouble, though ;)
>> This migrates all governors from module_init() to fs_initcall() when
>> being the default, as was already done in cpufreq_performance when it
>> was the only possible choice.
>
> Oh well. Which leads to more surprises in the future, I think...
It appears a bit hackish. I would be interested in a cleaner way to
force an earlier call to a module's init function.
Hannes
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists