Setting CPUFreq scaling governor to performance not setting CPU frequency to the highest

From: Vigneshwar S <svigneshj@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Setting CPUFreq scaling governor to performance not setting CPU frequency to the highest
Date: Tue, 5 Dec 2023 09:48:44 +0530	[thread overview]
Message-ID: <CAG+9GgQ8hry4i78ghYqsWBWoqRkCBiG1T7rFoCK0KsJ02MunRQ@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]

Hello everyone!

I've read about the CPU performance scaling in Linux kernel documentation
<https://docs.kernel.org/admin-guide/pm/cpufreq.html> and tried
experimenting with multiple scaling governors. Based on the documentation,
the performance scaling governor
<https://docs.kernel.org/admin-guide/pm/cpufreq.html#performance> should
set the frequency to the maximum possible frequency.

I've got two machines with different kernel versions: v3.10.0 (CentOS 7)
and v5.10.106 (Debian 11). When I set the 'scaling_governor' to
'performance' in the CentOS machine, it is working as expected and the CPU
frequency is set to the maximum possible frequency statically. But when I
set the 'scaling_governor' to 'performance' in the Debian machine, that's
not the case and the CPU frequency is changing dynamically.

I've read that 'intel_pstate' scaling driver would bypass the scaling
governor and set the CPU frequency based on its internal pstate
information. But in both CentOS and Debian machines, the 'scaling_driver'
is set to 'acpi-cpufreq' only.

How can I solve this? Any help on this would be greatly appreciated.

Thanks!

Vigneshwar S

[-- Attachment #1.2: Type: text/html, Size: 1345 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies