[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| howtos:hardware:cpu_frequency_scaling [2023/12/11 09:36 (UTC)] – [Kernel Configuration] zeebra | howtos:hardware:cpu_frequency_scaling [2023/12/11 10:43 (UTC)] (current) – [Introduction] zeebra | ||
|---|---|---|---|
| Line 9: | Line 9: | ||
| \\ | \\ | ||
| For older computers with " | For older computers with " | ||
| + | \\ | ||
| + | |||
| + | **Available governors** and the **currently used driver** can be seen by using the cpufreq command | ||
| + | < | ||
| \\ | \\ | ||
| ===== Kernel Configuration ===== | ===== Kernel Configuration ===== | ||
| Both Kernels (huge/ | Both Kernels (huge/ | ||
| - | If you want to use a newer Kernel series or your own Kernel, the relevant options are found in the section "Power management and ACPI options" | + | If you want to use a newer Kernel series or your own Kernel, the relevant options are found in the section |
| With AMD you should normally use the acpi-cpufreq driver, but exceptions apply. With Intel you will expose 3 different drivers: **intel_pstate**, | With AMD you should normally use the acpi-cpufreq driver, but exceptions apply. With Intel you will expose 3 different drivers: **intel_pstate**, | ||
| - | Generally speaking you could say that Intel P-state is performance biased in general and that acpi-cpufreq gives you the maximum control (including performance bias). There are several options you can pass to the Kernel at boot, but if you want to disable p-states and use the acpi-cpufreq driver you pass **intel_pstate=disable** to the Kernel at boot time. | + | Generally speaking you could say that Intel P-state is performance biased in general and that acpi-cpufreq gives you the maximum control (including performance bias). There are several options you can pass to the Kernel at boot, but if you want to disable p-states and use the acpi-cpufreq driver you pass **intel_pstate=disable** to the Kernel at boot time. These two options are the safe options, while other options could prevent a boot with certain CPU's. However, you might want to use another option depending on your cpu. \\ |
| + | \\ | ||
| + | You can pass these options at boot time to the Kernel command line with the bootloader, like Grub2, you add it after the Kernel line, the standard way of passing Kernel parameters at boot. | ||
| \\ | \\ | ||
| Line 23: | Line 29: | ||
| ===== / | ===== / | ||
| - | The main way to adjust frequency scaling in Slackware is to do so at boot time by making / | + | The main way to adjust frequency scaling in Slackware is to do so at boot time by making / |
| + | < | ||
| + | And by selecting the governor to use by editing the file / | ||
| + | < | ||
| + | < | ||
| + | # uncomment | ||
| + | # | ||
| + | </ | ||
| - | **Available governors** | + | <note important> |
| - | < | + | |
| After the initial setup of CPU frequency scaling at boot, scaling can also be controlled manually in a variety of ways, as described below.\\ | After the initial setup of CPU frequency scaling at boot, scaling can also be controlled manually in a variety of ways, as described below.\\ | ||
| Line 89: | Line 101: | ||
| <!-- You must remove the tag-word " | <!-- You must remove the tag-word " | ||
| <!-- Some updates done, more will follow. Specifically a section about /etc/rc.d/ is high priority | <!-- Some updates done, more will follow. Specifically a section about /etc/rc.d/ is high priority | ||
| - | {{tag> | + | {{tag> |
