Also it seems that ondemand was intentionally made to not work with
p4-clockmod, and that it is marked as depreciated and scheduled for
removal from the kernel.
commit 36e8abf3edcd2d207193ec5741d1a2a645d470a5
Author: Dave Jones <da...@redhat.com>
Date: Thu Mar 5 00:16:26 2009 -0500
[CPUFREQ] Prevent p4-clockmod from auto-binding to the ondemand
governor.
The latency of p4-clockmod sucks so hard that scaling on a regular
basis with ondemand is a really bad idea.
Signed-off-by: Matthew Garrett <mj...@srcf.ucam.org>
Signed-off-by: Dave Jones <da...@redhat.com>
commit e088e4c9cdb618675874becb91b2fd581ee707e6
Author: Matthew Garrett <m...@redhat.com>
Date: Tue Nov 25 13:29:47 2008 -0500
[CPUFREQ] Disable sysfs ui for p4-clockmod.
p4-clockmod has a long history of abuse. It pretends to be a CPU
frequency scaling driver, even though it doesn't actually change
the CPU frequency, but instead just modulates the frequency with
wait-states.
The biggest misconception is that when running at the lower 'frequency'
p4-clockmod is saving power. This isn't the case, as workloads running
slower take longer to complete, preventing the CPU from entering
deep C states.
However p4-clockmod does have a purpose. It can prevent overheating.
Having it hooked up to the cpufreq interfaces is the wrong way to
achieve
cooling however. It should instead be hooked up to ACPI.
This diff introduces a means for a cpufreq driver to register with the
cpufreq core, but not present a sysfs interface.
Signed-off-by: Matthew Garrett <m...@redhat.com>
Signed-off-by: Dave Jones <da...@redhat.com>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
