cpufreq-info - result005
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 1:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 2:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 3:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 4:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 5:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 6:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 7:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 8:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 9:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 10:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 11:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 12:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 13:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 14:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%
analyzing CPU 15:
driver: phytium_cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
CPUs which need to have their frequency coordinated by software: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
maximum transition latency: 2.00 ms.
hardware limits: 1000 MHz - 1.50 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1000 MHz and 1.50 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 1.50 GHz (asserted by call to hardware).
cpufreq stats: 1000 MHz:0.00%, 1.50 GHz:100.00%