16 Aug, 2011
1 commit
-
Which makes the implementation independent from cpufreq drivers.
Therefore this would also work on a Xen kernel where the hypervisor
is doing frequency switching and idle entering.Signed-off-by: Thomas Renninger
Signed-off-by: Dominik Brodowski
30 Jul, 2011
7 commits
-
IA32-Intel Devel guide Volume 3A - 14.3.2.1
-------------------------------------------
...
Opportunistic processor performance operation can be disabled by setting bit 38 of
IA32_MISC_ENABLES. This mechanism is intended for BIOS only. If
IA32_MISC_ENABLES[38] is set, CPUID.06H:EAX[1] will return 0.Better detect things via cpuid, this cleans up the code a bit
and the MSR parts were not working correctly anyway.Signed-off-by: Thomas Renninger
CC: lenb@kernel.org
CC: linux@dominikbrodowski.net
CC: cpufreq@vger.kernel.org
Signed-off-by: Dominik Brodowski -
This adds the last piece missing from turbostat (if called with -v).
It shows on Intel machines supporting Turbo Boost how many cores
have to be active/idle to enter which boost mode (frequency).Whether the HW really enters these boost modes can be verified via
./cpupower monitor.Signed-off-by: Thomas Renninger
CC: lenb@kernel.org
CC: linux@dominikbrodowski.net
CC: cpufreq@vger.kernel.org
Signed-off-by: Dominik Brodowski -
As cpupowerutils is intended to be included into the kernel sources,
use the kernel versioning instead of a custom version.The script utils/version-gen.sh is largely based on the script already
found in tools/perf/util/PERF-VERSION-GEN .Signed-off-by: Dominik Brodowski
-
Signed-off-by: Dominik Brodowski
-
Signed-off-by: Dominik Brodowski
-
Signed-off-by: Dominik Brodowski
-
CPU power consumption vs performance tuning is no longer
limited to CPU frequency switching anymore: deep sleep states,
traditional dynamic frequency scaling and hidden turbo/boost
frequencies are tied close together and depend on each other.
The first two exist on different architectures like PPC, Itanium and
ARM, the latter (so far) only on X86. On X86 the APU (CPU+GPU) will
only run most efficiently if CPU and GPU has proper power management
in place.Users and Developers want to have *one* tool to get an overview what
their system supports and to monitor and debug CPU power management
in detail. The tool should compile and work on as many architectures
as possible.Once this tool stabilizes a bit, it is intended to replace the
Intel-specific tools in tools/power/x86Signed-off-by: Dominik Brodowski
