[Bug 832179] Power management guide is wrong for frequency scaling in Fedora 17

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=832179

Jack Reed <jreed at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |MODIFIED
              Flags|                            |needinfo?(jskarvad at redhat.c
                   |                            |om)

--- Comment #3 from Jack Reed <jreed at redhat.com> ---
(In reply to comment #2)
> > 
> All are built-in and get selected automatically, so the text is obsoleted.
> So the "3.1 Procedure" should go away. The command:
> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> is useful and could be moved to 3.2.2 introduction, or maybe to 3.2
> procedure. Or just reuse/modify the text from the RHEL guide.
> 
> Also all governors are built-in, so preamble for 3.2 procedure is not right.

Thanks Jaroslav, but I'm unsure of what to edit. If I'm removing "If a specific
governor is not listed as available for your CPU" because those governors are
built in, then the whole step is redundant because it says to use modprobe to
enable a governor that is listed as unavailable for your CPU. If all governors
are listed as available, then I assume the modprobe command is unnecessary, in
which case the second step, which enables the governor, is all that's needed.
Should I delete the first step?

Note that because I am updating this section to incorporate the cpupower
command as we discussed, then this second step to enable the governor will use
"cpupower frequency-info --governors"

The command "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor" that
you've asked to be retained has also been replaced, by "cpupower frequency-info
--policy". 

I just want to be sure that this is acceptable and you don't actually want the
existing cat and echo commands to be retained despite the emphasis on cpupower.

> > 
> Everything is built-in in the kernel. The "important admon" should go away,
> the right module should be autoselected by kernel.

No problem - deleted.

> > 
> Right, it gone. AFAIK there is currently no replacement (I pointed this out
> in the past, but such scenarios are very rare and to be honest this is the
> way how it shouldn't be done).

Great, OK. I've removed the sentence "This governor is normally used in
conjunction with the cpuspeed daemon" from 3.2.1.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.