cpufreq-info - test2
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to [email protected], please.
analyzing CPU 0:
driver: amd-pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 1:
driver: amd-pstate
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 2:
driver: amd-pstate
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 5.14 GHz.
analyzing CPU 3:
driver: amd-pstate
CPUs which run at the same hardware frequency: 3
CPUs which need to have their frequency coordinated by software: 3
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 4:
driver: amd-pstate
CPUs which run at the same hardware frequency: 4
CPUs which need to have their frequency coordinated by software: 4
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.65 GHz.
analyzing CPU 5:
driver: amd-pstate
CPUs which run at the same hardware frequency: 5
CPUs which need to have their frequency coordinated by software: 5
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.65 GHz.
analyzing CPU 6:
driver: amd-pstate
CPUs which run at the same hardware frequency: 6
CPUs which need to have their frequency coordinated by software: 6
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 7:
driver: amd-pstate
CPUs which run at the same hardware frequency: 7
CPUs which need to have their frequency coordinated by software: 7
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.64 GHz.
analyzing CPU 8:
driver: amd-pstate
CPUs which run at the same hardware frequency: 8
CPUs which need to have their frequency coordinated by software: 8
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 5.14 GHz.
analyzing CPU 9:
driver: amd-pstate
CPUs which run at the same hardware frequency: 9
CPUs which need to have their frequency coordinated by software: 9
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 10:
driver: amd-pstate
CPUs which run at the same hardware frequency: 10
CPUs which need to have their frequency coordinated by software: 10
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 4.55 GHz.
analyzing CPU 11:
driver: amd-pstate
CPUs which run at the same hardware frequency: 11
CPUs which need to have their frequency coordinated by software: 11
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 4.55 GHz.
analyzing CPU 12:
driver: amd-pstate
CPUs which run at the same hardware frequency: 12
CPUs which need to have their frequency coordinated by software: 12
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 13:
driver: amd-pstate
CPUs which run at the same hardware frequency: 13
CPUs which need to have their frequency coordinated by software: 13
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 14:
driver: amd-pstate
CPUs which run at the same hardware frequency: 14
CPUs which need to have their frequency coordinated by software: 14
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.63 GHz.
analyzing CPU 15:
driver: amd-pstate
CPUs which run at the same hardware frequency: 15
CPUs which need to have their frequency coordinated by software: 15
maximum transition latency: 20.0 us.
hardware limits: 400 MHz - 5.14 GHz
available cpufreq governors: userspace, powersave, ondemand, conservative, performance, schedutil
current policy: frequency should be within 400 MHz and 5.14 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 3.64 GHz.