Building cpufreq modules into F16 kernel is it right or wrong?
contyk at redhat.com
Tue Oct 18 07:33:46 UTC 2011
On Mon, Oct 17, 2011 at 09:54:53PM +0300, alekcejk at googlemail.com wrote:
> The purpose of this bug was to provide native systemd script for cpuspeed in Fedora 16
> But instead of adding systemd script which should load cpufreq modules other
> solution was provided - cpufreq modules was compiled as built-in in Fedora 16 kernel.
> This decision was based on assumption that
> "kernel itself can really decide which cpufreq driver to use".
> But this assumption was wrong for my system which have BIOS option
> for disabling CPU frequency scaling (SpeedStep).
> If SpeedStep is enabled in BIOS then kernel uses acpi-cpufreq built-in module
> but if I will disable frequency scaling in BIOS kernel still loads cpufreq module
> but p4-clockmod instead of acpi-cpufreq.
> Such kernel behavior is not what expected because there is no way to
> really disable frequency scaling for me. So decision to compile cpufreq modules
> into kernel looks wrong for me and should be revised.
The right thing to do is to fix the kernel logic, not to bring back the
userspace initscript hacks we used to have.
Maybe there is a kernel argument to disable cpufreq stack completely for users
who really don't want it (i.e. you)? ...
# Petr Sabata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 230 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20111018/8be91837/attachment.bin
More information about the devel