RAPL-INFO(1) | rapl-info | RAPL-INFO(1) |
rapl-info - get RAPL configurations
rapl-info [OPTION]...
This utility is deprecated, use powercap-info(1) instead.
Prints out Intel Running Average Power Limit (RAPL) configurations.
Note that the -p and -z options are different from powercap-info(1).
This software requires an Intel processor (Sandy Bridge or newer), Linux kernel 3.13 or newer compiled with CONFIG_POWERCAP and CONFIG_INTEL_RAPL enabled, and the intel_rapl kernel module to be loaded.
The following are zone-level arguments (-z/--subzone is optional):
The following are constraint-level arguments and require -c/--constraint (-z/--subzone is optional):
Note that -p/--zone=0 is used by default when also specifying -z/--subzone and/or -c/--constraint, allowing for simpler commands on single-socket systems.
Some fields are optional and will only be printed if they are
available unless -v/--verbose is set.
If no zone/constraint-specific outputs are requested, all available zones and
constraints will be shown.
Energy units: microjoules (uJ)
Power units: microwatts (uW)
Time units: microseconds (us)
The following are behavioral quirks due to the kernel interface or abnormalities in some hardware. They are not bugs in rapl-info and should not be reported as such.
Values returned by the kernel sometimes lose accuracy from the actual values stored in Model-Specific Registers due to integer rounding. For example, the kernel may return a time window value of 7812 us, when in fact the actual stored value is 7812.5 us. Writing back a value returned by the kernel, e.g., using rapl-set(1), may cause unexpected changes to its value due to these rounding problems.
At the time of this writing, some features in the powercap
interface are not supported by RAPL. The following options may result in
ENOENT (No such file or directory) errors:
-w/--z-power
-W/--z-max-power-range
-u/--c-min-power
-T/--c-max-time-window
-t/--c-min-time-window
On some systems, the constraint max_power_uw file, e.g., constraint_0_max_power_uw, is known to receive an ENODATA (No data available) error from the kernel for subzones. So even though the file exists, a value may not be printed for it.
It is possible for packages on multi-socket systems to be indexed out of order by the kernel. For example, the package at index 0 (-p 0) could actually be named package-1 while the package at index 1 (-p 1) is named package-0.
Report bugs upstream at <https://github.com/powercap/powercap>
/sys/devices/virtual/powercap/intel-rapl/*
/sys/class/powercap/intel-rapl/*
Connor Imes <connor.k.imes@gmail.com>
2021-04-14 | powercap |