cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.71 GHz (asserted by call to hardware). analyzing CPU 1: driver: intel_pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.70 GHz (asserted by call to hardware). analyzing CPU 2: driver: intel_pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.71 GHz (asserted by call to hardware). analyzing CPU 3: driver: intel_pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.70 GHz (asserted by call to hardware). analyzing CPU 4: driver: intel_pstate CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.70 GHz (asserted by call to hardware). analyzing CPU 5: driver: intel_pstate CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.73 GHz (asserted by call to hardware). analyzing CPU 6: driver: intel_pstate CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.71 GHz (asserted by call to hardware). analyzing CPU 7: driver: intel_pstate CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 0.97 ms. hardware limits: 1.60 GHz - 3.90 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.60 GHz and 3.90 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 3.72 GHz (asserted by call to hardware).

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. Usage: cpufreq-info [options] Options: -c CPU, --cpu CPU CPU number which information shall be determined about -e, --debug Prints out debug information -f, --freq Get frequency the CPU currently runs at, according to the cpufreq core * -w, --hwfreq Get frequency the CPU currently runs at, by reading it from hardware (only available to root) * -l, --hwlimits Determine the minimum and maximum CPU frequency allowed * -d, --driver Determines the used cpufreq kernel driver * -p, --policy Gets the currently used cpufreq policy * -g, --governors Determines available cpufreq governors * -r, --related-cpus Determines which CPUs run at the same hardware frequency * -a, --affected-cpus Determines which CPUs need to have their frequency coordinated by software * -s, --stats Shows cpufreq statistics if available -y, --latency Determines the maximum latency on CPU frequency changes * -o, --proc Prints out information like provided by the /proc/cpufreq interface in 2.4. and early 2.6. kernels -m, --human human-readable output for the -f, -w, -s and -y parameters -h, --help Prints out this screen If no argument or only the -c, --cpu parameter is given, debug output about cpufreq is printed which is useful e.g. for reporting bugs. For the arguments marked with *, omitting the -c or --cpu argument is equivalent to setting it to zero