How to make use of Dynamic Frequency Scaling
Linux supports dynamic frequency scaling for systems with the following processors:
- Intel Mobile Pentium III
- Intel Mobile Pentium III-M
- Intel Mobile Pentium 4
- Intel Mobile Pentium 4-M
- Intel Pentium M (Banias)
- Intel Pentium M (Dothan)
- Intel Core Solo (Yonah)
- Intel Core Duo (Yonah)
- Intel Core 2 Duo
- Mobile Athlon
- Via C3
- Via C7
Configuring the Kernel
You need to enable the CPU frequency scaling for your kernel (usually your distros kernel will have this enabled), under Power management options (ACPI, APM) → CPU Frequency scaling → : <*> (CONFIG_CPU_FREQ)
If you own a Dothan processor, you need to enable Enhanced SpeedStep functionalities.
- <*> (CONFIG_X86_SPEEDSTEP_CENTRINO)
Alternatively, there seems to be some advocacy of a switch over to
- <*> (CONFIG_X86_ACPI_CPUFREQ)
for controlling speedstep technology. Apparently this newer kernel option is more aware of acpi powersaving that's done in the BIOS. In any case, both <*> (CONFIG_X86_SPEEDSTEP_CENTRINO) and <*> (CCONFIG_X86_ACPI_CPUFREQ) were found to work on a Menrom (Core 2).
You also need to enable governors, if not already done in your distros default kernel:
- <*> (CONFIG_CPU_FREQ_GOV_PERFORMANCE)
The performance CPU governor lets your CPU frequency always to the highest available.
- <*> (CONFIG_CPU_FREQ_GOV_POWERSAVE)
The powersave governor sets the frequency to the lowest available. That's not the best choice for battery lifetime on modern Intel CPU, though (see above).
- <*> (CONFIG_CPU_FREQ_GOV_USERSPACE)
The userspace governor allows you to set the frequency manually, unlike the others. Some frequency scaling daemons require this governor to operate correctly. This is typically the recommended option with older processors like A30p's pIIIm-1200.
- <*> (CONFIG_CPU_FREQ_GOV_ONDEMAND)
- <*> (CONFIG_CPU_FREQ_GOV_CONSERVATIVE)
The ondemand (available since 2.6.10) and conservative (since 2.6.12) are governors based on in kernel implementations of CPU scaling algorithms: they scale the CPU frequencies according to the needs (like does the userspace frequency scaling daemons, but in kernel). They differs in the way they scale up and down. The ondemand governor switches to the highest frequency immediately when there is load, while the conservative governor increases frequency step by step. Likewise they behave the other way round for stepping down frequency when the CPU is idle. The conservative governor is good for battery powered environments on AMD64 (but may not work on older ThinkPads like the T21). Ondemand may not work on older laptops without Enhanced SpeedStep due to latency reasons. Anyway, for recent enough Intel CPU, ondemand is the one recommended for power efficiency (over userspace, and even over "powersave") by the Intel's kernel developer Arjan van de Ven (see , , )
2.6 doing it with modules
With the Debian flavour of 2.6.21 and possibly earlier versions as well as other distros, all of the above kernel options are compiled as modules out of the box. You'll have to load them yourself to get speedstep functionality. This can be done simply enough in an /etc/modules file with the lines
acpi-cpufreq cpufreq_ondemand cpufreq_userspace cpufreq_conservative cpufreq_powersave
of course, this is a bit excessive if you're only going to use one governor (see below), you only need to load the modules for the governor(s) you are going to use. It seems that "performance" is not a loadable module in my case. Probably because it's built into the kernel as the default. Finally if you're a fan of useless statistics, you can load cpufreq_stats so that you can see how long your processor spends in each state and how many times it transitions with
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/total_trans cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
With kernel >=2.6.31, possibly some versions below that, different CPUFreq processor drivers are added.
- "powernow-k8" is the frequency scaling module for AMD processors and
- "acpi-cpufreq" looks like the right choose for INTEL processors, though there is a more aggressive method for P4 and XEON processors called
- "p4-clockmod". But the last can cause slowdowns and latencies, so you really should read your kernels Handbook Documentation/cpu-freq/ on this.
Using the Sys Interface
The files in /sys/devices/system/cpu/cpu0/cpufreq/ provide information and a means of controlling the frequency scaling subsystem. Seed values are given in Khz. You need to be root to access the /sys filesystem.
Your max speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq.
# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq
Your min speed is at /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq.
# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq
If you are using the userspace governor, you can write to /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed to change the current speed.
# echo 700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
# cat /proc/cpuinfo
cpu MHz : 697.252
# echo 900000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
# cat /proc/cpuinfo
cpu MHz : 976.152
Using Frequency Scaling Governors
You can get a list of available governors with (as root):
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
conservative ondemand powersave userspace performance
Note: If the governors are compiled as modules, load them first:
# modprobe cpufreq_performance cpufreq_ondemand cpufreq_conservative cpufreq_powersave cpufreq_userspace
Now we set our governor: What is our current governor?
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Set new governor and watch if it has changed
# echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Congrats! Your governor is active.
You may set the governor in your rc.local, to make it used on every boot.
Using Frequency Scaling Daemons
Frequency Scaling Daemons adapt the frequency policy to different situations. A typical configuration would be to use the ondemand governor running off batteries and performance otherwise, or combining powersave with conservative on laptops with heat problems. More sophisticated setups adapt to battery level, CPU temperature or even running programs. Some daemons are able to control other power management features like hard disks or graphic cards.
Some daemons use the kernel governors (see above), others implement the functionality on their own. In the latter case you have to enable the userspace governor. If it is built as module, load it as cpufreq-userspace.
There are plenty of userspace frequency scaling daemons available:
- laptop-mode-tools can also be configured to switch governors when the laptop is plugged in and unplugged
Instead of compiling your own kernel, you can use the Debian "stock" kernel. In Debian/Etch the 2.6.18 kernel image with an /etc/modules file that includes:
battery ac thermal processor acpi-cpufreq cpufreq-userspace
With the powernowd package and you should be setup.
Debian Etch now has rc.local (see package initscripts).
However, a better alternative for Debian, rather than modifying bootscripts, is to install the sysfsutils package. Then edit /etc/sysfs.conf (as root), where you can setup values to sysfs entries that you want to be modified automatically on boot.
- If you have a Coppermine-piix-smi based ThinkPads like from the A2x, X2x and T2x series you need to enable the speedstep-smi driver in the kernel and load it if it's built as module. You might want to look at this page.
- If you have a p4-class celeron based ThinkPad like the R40e you might want to look at this page
- You may need to set your BIOS to "maximum performance" if you are using Linux to set the CPU speed. This is necessary to prevent odd behaviour (cpufreq 'freezing' at certain frequencies) with the T4x series.
- You will need to have the cpufreq-selector applet installed at SUID root to use the gnome cpufreq applet. See this page for info.
- If you have a thinkpad with intel core i3/5/7 cpu, and it always runs at lowest speed, see Problem with CPU frequency scaling
Finetuning voltages and available frequencies
A note about CPU throttling
Throttling the CPU through ACPI "T" states is generally useless for power consumption reduction nowadays. It is an artifact of the past, when there was no clock frequency scaling and ACPI "C" states were mostly not implemented or didn't exist.
Throttling does not decrease clock frequency at all, and it can even increase power consumption in a modern CPU capable of ACPI "C" states, as it can interfere with the CPU reaching the higher C states (such as C2).
On a T43, setting a CPU to a ACPI Throttle state different than T0 (no throttling) can cause it to draw more than 100mW extra power, as it will reach C2 less often.
In case your BIOS offers "cpu power management" and "pci bus power management" disabled by default (that's the case in X40 with the 2.08 BIOS), you should turn them on (or choose "automatic"). Despite what the BIOS online documentation says ("rarely needed"), this is quite useful, since it make the deepests (C3 and C4) ACPI C-states avaibles. On a kernel more with dynticks (2.6.21 and over), this should save about 2W or more.
- The Ondemand Governor, Intel Open Source Technology Center (Venkatesh Pallipadi, Alexey Starikovskiy, Len Brown), presentation at Ottawa Linux Symposium, July 19 2006