aboutsummaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorLen Brown <len.brown@intel.com>2017-02-15 00:30:22 -0500
committerLen Brown <len.brown@intel.com>2017-03-01 00:14:23 -0500
commitda67e2b9fd1d846a41978690da0a899d8e4378ec (patch)
tree853d437bcbcea289367231534c44a4bc3b0e8509 /tools
parent6168c2e0fb5084d187aa8f3ec4093db5e161d4dc (diff)
tools/power turbostat: turbostat.8 update
update examples to show recently updated features. In particular --add --show --hide --cpu --list Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'tools')
-rw-r--r--tools/power/x86/turbostat/turbostat.8238
1 files changed, 140 insertions, 98 deletions
diff --git a/tools/power/x86/turbostat/turbostat.8 b/tools/power/x86/turbostat/turbostat.8
index efe6a7147ff2..b1b1ab80102c 100644
--- a/tools/power/x86/turbostat/turbostat.8
+++ b/tools/power/x86/turbostat/turbostat.8
@@ -16,9 +16,9 @@ idle power-state statistics, temperature and power on X86 processors.
16There are two ways to invoke turbostat. 16There are two ways to invoke turbostat.
17The first method is to supply a 17The first method is to supply a
18\fBcommand\fP, which is forked and statistics are printed 18\fBcommand\fP, which is forked and statistics are printed
19upon its completion. 19in one-shot upon its completion.
20The second method is to omit the command, 20The second method is to omit the command,
21and turbostat displays statistics every 5 seconds. 21and turbostat displays statistics every 5 seconds interval.
22The 5-second interval can be changed using the --interval option. 22The 5-second interval can be changed using the --interval option.
23.PP 23.PP
24Some information is not available on older processors. 24Some information is not available on older processors.
@@ -28,9 +28,10 @@ name as necessary to disambiguate it from others is necessary. Note that option
28.PP 28.PP
29\fB--add attributes\fP add column with counter having specified 'attributes'. The 'location' attribute is required, all others are optional. 29\fB--add attributes\fP add column with counter having specified 'attributes'. The 'location' attribute is required, all others are optional.
30.nf 30.nf
31 location: {\fBmsrDDD\fP | \fBmsr0xXXX\fP} 31 location: {\fBmsrDDD\fP | \fBmsr0xXXX\fP | \fB/sys/path...\fP}
32 msrDDD is a decimal offset, eg. msr16 32 msrDDD is a decimal offset, eg. msr16
33 msr0xXXX is a hex offset, eg. msr0x10 33 msr0xXXX is a hex offset, eg. msr0x10
34 /sys/path... is an absolute path to a sysfs attribute
34 35
35 scope: {\fBcpu\fP | \fBcore\fP | \fBpackage\fP} 36 scope: {\fBcpu\fP | \fBcore\fP | \fBpackage\fP}
36 sample and print the counter for every cpu, core, or package. 37 sample and print the counter for every cpu, core, or package.
@@ -45,6 +46,10 @@ name as necessary to disambiguate it from others is necessary. Note that option
45 'delta' shows the difference in values during the measurement interval. 46 'delta' shows the difference in values during the measurement interval.
46 'percent' shows the delta as a percentage of the cycles elapsed. 47 'percent' shows the delta as a percentage of the cycles elapsed.
47 default: delta 48 default: delta
49
50 name: "name_string"
51 Any string that does not match a key-word above is used
52 as the column header.
48.fi 53.fi
49.PP 54.PP
50\fB--cpu cpu-set\fP limit output to system summary plus the specified cpu-set. cpu-set is a comma delimited list of cpu ranges. cpu ranges can be individual cpu numbers or start and end numbers, separated by ".." or '-'. eg. 1,2,8,14..17,21-44 55\fB--cpu cpu-set\fP limit output to system summary plus the specified cpu-set. cpu-set is a comma delimited list of cpu ranges. cpu ranges can be individual cpu numbers or start and end numbers, separated by ".." or '-'. eg. 1,2,8,14..17,21-44
@@ -68,6 +73,8 @@ The file is truncated if it already exists, and it is created if it does not exi
68.PP 73.PP
69\fB--Package\fP limits output to the system summary plus the 1st thread in each Package. 74\fB--Package\fP limits output to the system summary plus the 1st thread in each Package.
70.PP 75.PP
76\fB--list\fP display column header names available for use by --show and --hide, then exit.
77.PP
71\fB--processor\fP limits output to the system summary plus the 1st thread in each processor of each package. Ie. it skips hyper-threaded siblings. 78\fB--processor\fP limits output to the system summary plus the 1st thread in each processor of each package. Ie. it skips hyper-threaded siblings.
72.PP 79.PP
73\fB--Summary\fP limits output to a 1-line System Summary for each interval. 80\fB--Summary\fP limits output to a 1-line System Summary for each interval.
@@ -79,24 +86,25 @@ The file is truncated if it already exists, and it is created if it does not exi
79The \fBcommand\fP parameter forks \fBcommand\fP, and upon its exit, 86The \fBcommand\fP parameter forks \fBcommand\fP, and upon its exit,
80displays the statistics gathered since it was forked. 87displays the statistics gathered since it was forked.
81.PP 88.PP
82.SH DEFAULT FIELD DESCRIPTIONS 89.SH ROW DESCRIPTIONS
90The system configuration dump (if --quiet is not used) is followed by statistics. The first row of the statistics labels the content of each column (below). The second row of statistics is the system summary line. The system summary line has a '-' in the columns for the Package, Core, and CPU. The contents of the system summary line depends on the type of column. Columns that count items (eg. IRQ) show the sum across all CPUs in the system. Columns that show a percentage show the average across all CPUs in the system. Columns that dump raw MSR values simply show 0 in the summary. After the system summary row, each row describes a specific Package/Core/CPU. Note that if the --cpu parameter is used to limit which specific CPUs are displayed, turbostat will still collect statistics for all CPUs in the system and will still show the system summary for all CPUs in the system.
91.SH COLUMN DESCRIPTIONS
83.nf 92.nf
93\fBCore\fP processor core number. Note that multiple CPUs per core indicate support for Intel(R) Hyper-Threading Technology (HT).
84\fBCPU\fP Linux CPU (logical processor) number. Yes, it is okay that on many systems the CPUs are not listed in numerical order -- for efficiency reasons, turbostat runs in topology order, so HT siblings appear together. 94\fBCPU\fP Linux CPU (logical processor) number. Yes, it is okay that on many systems the CPUs are not listed in numerical order -- for efficiency reasons, turbostat runs in topology order, so HT siblings appear together.
85\fBAVG_MHz\fP number of cycles executed divided by time elapsed. 95\fBPackage\fP processor package number -- not present on systems with a single processor package.
86\fBBusy%\fP percent of the interval that the CPU retired instructions, aka. % of time in "C0" state. 96\fBAvg_MHz\fP number of cycles executed divided by time elapsed. Note that this includes idle-time when 0 instructions are executed.
87\fBBzy_MHz\fP average clock rate while the CPU was busy (in "c0" state). 97\fBBusy%\fP percent of the measurement interval that the CPU executes instructions, aka. % of time in "C0" state.
98\fBBzy_MHz\fP average clock rate while the CPU was not idle (ie. in "c0" state).
88\fBTSC_MHz\fP average MHz that the TSC ran during the entire interval. 99\fBTSC_MHz\fP average MHz that the TSC ran during the entire interval.
89.fi 100\fBIRQ\fP The number of interrupts serviced by that CPU during the measurement interval. The system total line is the sum of interrupts serviced across all CPUs. turbostat parses /proc/interrupts to generate this summary.
90.PP 101\fBSMI\fP The number of System Management Interrupts serviced CPU during the measurement interval. While this counter is actually per-CPU, SMI are triggered on all processors, so the number should be the same for all CPUs.
91.SH DEBUG FIELD DESCRIPTIONS 102\fBC1, C2, C3...\fP The number times Linux requested the C1, C2, C3 idle state during the measurement interval. The system summary line shows the sum for all CPUs. These are C-state names as exported in /sys/devices/system/cpu/cpu*/cpuidle/state*/name. While their names are generic, their attributes are processor specific. They the system description section of output shows what MWAIT sub-states they are mapped to on each system.
92.nf 103\fBC1%, C2%, C3%\fP The residency percentage that Linux requested C1, C2, C3.... The system summary is the average of all CPUs in the system. Note that these are software, reflecting what was requested. The hardware counters reflect what was actually achieved.
93\fBPackage\fP processor package number. 104\fBCPU%c1, CPU%c3, CPU%c6, CPU%c7\fP show the percentage residency in hardware core idle states. These numbers are from hardware residency counters.
94\fBCore\fP processor core number.
95Note that multiple CPUs per core indicate support for Intel(R) Hyper-Threading Technology (HT).
96\fBCPU%c1, CPU%c3, CPU%c6, CPU%c7\fP show the percentage residency in hardware core idle states.
97\fBCoreTmp\fP Degrees Celsius reported by the per-core Digital Thermal Sensor. 105\fBCoreTmp\fP Degrees Celsius reported by the per-core Digital Thermal Sensor.
98\fBPkgTtmp\fP Degrees Celsius reported by the per-package Package Thermal Monitor. 106\fBPkgTtmp\fP Degrees Celsius reported by the per-package Package Thermal Monitor.
99\fBPkg%pc2, Pkg%pc3, Pkg%pc6, Pkg%pc7\fP percentage residency in hardware package idle states. 107\fBPkg%pc2, Pkg%pc3, Pkg%pc6, Pkg%pc7\fP percentage residency in hardware package idle states. These numbers are from hardware residency counters.
100\fBPkgWatt\fP Watts consumed by the whole package. 108\fBPkgWatt\fP Watts consumed by the whole package.
101\fBCorWatt\fP Watts consumed by the core part of the package. 109\fBCorWatt\fP Watts consumed by the core part of the package.
102\fBGFXWatt\fP Watts consumed by the Graphics part of the package -- available only on client processors. 110\fBGFXWatt\fP Watts consumed by the Graphics part of the package -- available only on client processors.
@@ -104,50 +112,110 @@ Note that multiple CPUs per core indicate support for Intel(R) Hyper-Threading T
104\fBPKG_%\fP percent of the interval that RAPL throttling was active on the Package. 112\fBPKG_%\fP percent of the interval that RAPL throttling was active on the Package.
105\fBRAM_%\fP percent of the interval that RAPL throttling was active on DRAM. 113\fBRAM_%\fP percent of the interval that RAPL throttling was active on DRAM.
106.fi 114.fi
115.SH TOO MUCH INFORMATION EXAMPLE
116By default, turbostat dumps all possible information -- a system configuration header, followed by columns for all counters.
117This is ideal for remote debugging, use the "--out" option to save everything to a text file, and get that file to the expert helping you debug.
107.PP 118.PP
108.SH PERIODIC EXAMPLE 119When you are not interested in all that information, and there are several ways to see only what you want. First the "--quiet" option will skip the configuration information, and turbostat will show only the counter columns. Second, you can reduce the columns with the "--hide" and "--show" options. If you use the "--show" option, then turbostat will show only the columns you list. If you use the "--hide" option, turbostat will show all columns, except the ones you list.
109Without any parameters, turbostat displays statistics ever 5 seconds. 120.PP
110Periodic output goes to stdout, by default, unless --out is used to specify an output file. 121To find out what columns are available for --show and --hide, the "--list" option is available. Note, however, there is an exception. The C-state columns collected from sysfs "C1,C2,C3,C1%,C2%,C3%" are not built-in counters, but are discovered after --show and --hide are processed. You can use the special counter name "sysfs" to refer to all of them at the same time.
111The 5-second interval can be changed with th "-i sec" option. 122.nf
112Or a command may be specified as in "FORK EXAMPLE" below. 123sudo ./turbostat --show sysfs --quiet sleep 10
12410.003837 sec
125 C1 C1E C3 C6 C7s C1% C1E% C3% C6% C7s%
126 4 21 2 2 459 0.14 0.82 0.00 0.00 98.93
127 1 17 2 2 130 0.00 0.02 0.00 0.00 99.80
128 0 0 0 0 31 0.00 0.00 0.00 0.00 99.95
129 2 1 0 0 52 1.14 6.49 0.00 0.00 92.21
130 1 2 0 0 52 0.00 0.08 0.00 0.00 99.86
131 0 0 0 0 71 0.00 0.00 0.00 0.00 99.89
132 0 0 0 0 25 0.00 0.00 0.00 0.00 99.96
133 0 0 0 0 74 0.00 0.00 0.00 0.00 99.94
134 0 1 0 0 24 0.00 0.00 0.00 0.00 99.84
135.fi
136.PP
137.SH ONE SHOT COMMAND EXAMPLE
138If turbostat is invoked with a command, it will fork that command
139and output the statistics gathered after the command exits.
140In this case, turbostat output goes to stderr, by default.
141Output can instead be saved to a file using the --out option.
142In this example, the "sleep 10" command is forked, and turbostat waits for it to complete before saving all statistics into "ts.out". Note that "sleep 10" is not part of turbostat, but is simply an example of a command that turbostat can fork. The "ts.out" file is what you want to edit in a very wide window, paste into a spreadsheet, or attach to a bugzilla entry.
143
113.nf 144.nf
114[root@hsw]# ./turbostat 145[root@hsw]# ./turbostat -o ts.out sleep 10
115 CPU Avg_MHz Busy% Bzy_MHz TSC_MHz 146[root@hsw]#
116 - 488 12.51 3898 3498 147.fi
117 0 0 0.01 3885 3498
118 4 3897 99.99 3898 3498
119 1 0 0.00 3861 3498
120 5 0 0.00 3882 3498
121 2 1 0.02 3894 3498
122 6 2 0.06 3898 3498
123 3 0 0.00 3849 3498
124 7 0 0.00 3877 3498
125 148
149.SH PERIODIC INTERVAL EXAMPLE
150Without a command to fork, turbostat displays statistics ever 5 seconds.
151Periodic output goes to stdout, by default, unless --out is used to specify an output file.
152The 5-second interval can be changed with the "-i sec" option.
153.nf
154sudo ./turbostat --quiet --hide sysfs,IRQ,SMI,CoreTmp,PkgTmp,GFX%rc6,GFXMHz,PkgWatt,CorWatt,GFXWatt
155 Core CPU Avg_MHz Busy% Bzy_MHz TSC_MHz CPU%c1 CPU%c3 CPU%c6 CPU%c7
156 - - 488 12.52 3900 3498 12.50 0.00 0.00 74.98
157 0 0 5 0.13 3900 3498 99.87 0.00 0.00 0.00
158 0 4 3897 99.99 3900 3498 0.01
159 1 1 0 0.00 3856 3498 0.01 0.00 0.00 99.98
160 1 5 0 0.00 3861 3498 0.01
161 2 2 1 0.02 3889 3498 0.03 0.00 0.00 99.95
162 2 6 0 0.00 3863 3498 0.05
163 3 3 0 0.01 3869 3498 0.02 0.00 0.00 99.97
164 3 7 0 0.00 3878 3498 0.03
165 Core CPU Avg_MHz Busy% Bzy_MHz TSC_MHz CPU%c1 CPU%c3 CPU%c6 CPU%c7
166 - - 491 12.59 3900 3498 12.42 0.00 0.00 74.99
167 0 0 27 0.69 3900 3498 99.31 0.00 0.00 0.00
168 0 4 3898 99.99 3900 3498 0.01
169 1 1 0 0.00 3883 3498 0.01 0.00 0.00 99.99
170 1 5 0 0.00 3898 3498 0.01
171 2 2 0 0.01 3889 3498 0.02 0.00 0.00 99.98
172 2 6 0 0.00 3889 3498 0.02
173 3 3 0 0.00 3856 3498 0.01 0.00 0.00 99.99
174 3 7 0 0.00 3897 3498 0.01
126.fi 175.fi
127.SH DEBUG EXAMPLE 176This example also shows the use of the --hide option to skip columns that are not wanted.
177Note that cpu4 in this example is 99.99% busy, while the other CPUs are all under 1% busy.
178Notice that cpu4's HT sibling is cpu0, which is under 1% busy, but can get into CPU%c1 only,
179because its cpu4's activity on shared hardware keeps it from entering a deeper C-state.
180
181.SH SYSTEM CONFIGURATION INFORMATION EXAMPLE
128 182
129The first row of statistics is a summary for the entire system. 183By default, turbostat always dumps system configuration information
130For residency % columns, the summary is a weighted average. 184before taking measurements. In the example above, "--quiet" is used
131For Temperature columns, the summary is the column maximum. 185to suppress that output. Here is an example of the configuration information:
132For Watts columns, the summary is a system total.
133Subsequent rows show per-CPU statistics.
134.nf 186.nf
135turbostat version 4.1 10-Feb, 2015 - Len Brown <lenb@kernel.org> 187turbostat version 2017.02.15 - Len Brown <lenb@kernel.org>
136CPUID(0): GenuineIntel 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3) 188CPUID(0): GenuineIntel 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3)
137CPUID(6): APERF, DTS, PTM, EPB 189CPUID(1): SSE3 MONITOR - EIST TM2 TSC MSR ACPI-TM TM
190CPUID(6): APERF, TURBO, DTS, PTM, No-HWP, No-HWPnotify, No-HWPwindow, No-HWPepp, No-HWPpkg, EPB
191cpu4: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST No-MWAIT PREFETCH TURBO)
192CPUID(7): No-SGX
193cpu4: MSR_MISC_PWR_MGMT: 0x00400000 (ENable-EIST_Coordination DISable-EPB DISable-OOB)
138RAPL: 3121 sec. Joule Counter Range, at 84 Watts 194RAPL: 3121 sec. Joule Counter Range, at 84 Watts
139cpu0: MSR_NHM_PLATFORM_INFO: 0x80838f3012300 195cpu4: MSR_PLATFORM_INFO: 0x80838f3012300
1408 * 100 = 800 MHz max efficiency 1968 * 100.0 = 800.0 MHz max efficiency frequency
14135 * 100 = 3500 MHz TSC frequency 19735 * 100.0 = 3500.0 MHz base frequency
142cpu0: MSR_IA32_POWER_CTL: 0x0004005d (C1E auto-promotion: DISabled) 198cpu4: MSR_IA32_POWER_CTL: 0x0004005d (C1E auto-promotion: DISabled)
143cpu0: MSR_NHM_SNB_PKG_CST_CFG_CTL: 0x1e000400 (UNdemote-C3, UNdemote-C1, demote-C3, demote-C1, UNlocked: pkg-cstate-limit=0: pc0) 199cpu4: MSR_TURBO_RATIO_LIMIT: 0x25262727
144cpu0: MSR_TURBO_RATIO_LIMIT: 0x25262727 20037 * 100.0 = 3700.0 MHz max turbo 4 active cores
14537 * 100 = 3700 MHz max turbo 4 active cores 20138 * 100.0 = 3800.0 MHz max turbo 3 active cores
14638 * 100 = 3800 MHz max turbo 3 active cores 20239 * 100.0 = 3900.0 MHz max turbo 2 active cores
14739 * 100 = 3900 MHz max turbo 2 active cores 20339 * 100.0 = 3900.0 MHz max turbo 1 active cores
14839 * 100 = 3900 MHz max turbo 1 active cores 204cpu4: MSR_CONFIG_TDP_NOMINAL: 0x00000023 (base_ratio=35)
205cpu4: MSR_CONFIG_TDP_LEVEL_1: 0x00000000 ()
206cpu4: MSR_CONFIG_TDP_LEVEL_2: 0x00000000 ()
207cpu4: MSR_CONFIG_TDP_CONTROL: 0x80000000 ( lock=1)
208cpu4: MSR_TURBO_ACTIVATION_RATIO: 0x00000000 (MAX_NON_TURBO_RATIO=0 lock=0)
209cpu4: MSR_PKG_CST_CONFIG_CONTROL: 0x1e000400 (UNdemote-C3, UNdemote-C1, demote-C3, demote-C1, UNlocked: pkg-cstate-limit=0: pc0)
210cpu4: POLL: CPUIDLE CORE POLL IDLE
211cpu4: C1: MWAIT 0x00
212cpu4: C1E: MWAIT 0x01
213cpu4: C3: MWAIT 0x10
214cpu4: C6: MWAIT 0x20
215cpu4: C7s: MWAIT 0x32
216cpu4: MSR_MISC_FEATURE_CONTROL: 0x00000000 (L2-Prefetch L2-Prefetch-pair L1-Prefetch L1-IP-Prefetch)
149cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x00000006 (balanced) 217cpu0: MSR_IA32_ENERGY_PERF_BIAS: 0x00000006 (balanced)
150cpu0: MSR_CORE_PERF_LIMIT_REASONS, 0x31200000 (Active: ) (Logged: Auto-HWP, Amps, MultiCoreTurbo, Transitions, ) 218cpu0: MSR_CORE_PERF_LIMIT_REASONS, 0x31200000 (Active: ) (Logged: Transitions, MultiCoreTurbo, Amps, Auto-HWP, )
151cpu0: MSR_GFX_PERF_LIMIT_REASONS, 0x00000000 (Active: ) (Logged: ) 219cpu0: MSR_GFX_PERF_LIMIT_REASONS, 0x00000000 (Active: ) (Logged: )
152cpu0: MSR_RING_PERF_LIMIT_REASONS, 0x0d000000 (Active: ) (Logged: Amps, PkgPwrL1, PkgPwrL2, ) 220cpu0: MSR_RING_PERF_LIMIT_REASONS, 0x0d000000 (Active: ) (Logged: Amps, PkgPwrL1, PkgPwrL2, )
153cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.000061 Joules, 0.000977 sec.) 221cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.000061 Joules, 0.000977 sec.)
@@ -162,23 +230,14 @@ cpu0: MSR_PP1_POLICY: 0
162cpu0: MSR_PP1_POWER_LIMIT: 0x00000000 (UNlocked) 230cpu0: MSR_PP1_POWER_LIMIT: 0x00000000 (UNlocked)
163cpu0: GFX Limit: DISabled (0.000000 Watts, 0.000977 sec, clamp DISabled) 231cpu0: GFX Limit: DISabled (0.000000 Watts, 0.000977 sec, clamp DISabled)
164cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x00641400 (100 C) 232cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x00641400 (100 C)
165cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x88340800 (48 C) 233cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x884c0800 (24 C)
166cpu0: MSR_IA32_THERM_STATUS: 0x88340000 (48 C +/- 1) 234cpu0: MSR_IA32_THERM_STATUS: 0x884c0000 (24 C +/- 1)
167cpu1: MSR_IA32_THERM_STATUS: 0x88440000 (32 C +/- 1) 235cpu1: MSR_IA32_THERM_STATUS: 0x88510000 (19 C +/- 1)
168cpu2: MSR_IA32_THERM_STATUS: 0x88450000 (31 C +/- 1) 236cpu2: MSR_IA32_THERM_STATUS: 0x884e0000 (22 C +/- 1)
169cpu3: MSR_IA32_THERM_STATUS: 0x88490000 (27 C +/- 1) 237cpu3: MSR_IA32_THERM_STATUS: 0x88510000 (19 C +/- 1)
170 Core CPU Avg_MHz Busy% Bzy_MHz TSC_MHz SMI CPU%c1 CPU%c3 CPU%c6 CPU%c7 CoreTmp PkgTmp PkgWatt CorWatt GFXWatt 238cpu4: MSR_PKGC3_IRTL: 0x00008842 (valid, 67584 ns)
171 - - 493 12.64 3898 3498 0 12.64 0.00 0.00 74.72 47 47 21.62 13.74 0.00 239cpu4: MSR_PKGC6_IRTL: 0x00008873 (valid, 117760 ns)
172 0 0 4 0.11 3894 3498 0 99.89 0.00 0.00 0.00 47 47 21.62 13.74 0.00 240cpu4: MSR_PKGC7_IRTL: 0x00008891 (valid, 148480 ns)
173 0 4 3897 99.98 3898 3498 0 0.02
174 1 1 7 0.17 3887 3498 0 0.04 0.00 0.00 99.79 32
175 1 5 0 0.00 3885 3498 0 0.21
176 2 2 29 0.76 3895 3498 0 0.10 0.01 0.01 99.13 32
177 2 6 2 0.06 3896 3498 0 0.80
178 3 3 1 0.02 3832 3498 0 0.03 0.00 0.00 99.95 28
179 3 7 0 0.00 3879 3498 0 0.04
180^C
181
182.fi 241.fi
183The \fBmax efficiency\fP frequency, a.k.a. Low Frequency Mode, is the frequency 242The \fBmax efficiency\fP frequency, a.k.a. Low Frequency Mode, is the frequency
184available at the minimum package voltage. The \fBTSC frequency\fP is the base 243available at the minimum package voltage. The \fBTSC frequency\fP is the base
@@ -188,39 +247,22 @@ should be sustainable on all CPUs indefinitely, given nominal power and cooling.
188The remaining rows show what maximum turbo frequency is possible 247The remaining rows show what maximum turbo frequency is possible
189depending on the number of idle cores. Note that not all information is 248depending on the number of idle cores. Note that not all information is
190available on all processors. 249available on all processors.
191.SH FORK EXAMPLE 250.SH ADD COUNTER EXAMPLE
192If turbostat is invoked with a command, it will fork that command 251Here we limit turbostat to showing just the CPU number for cpu0 - cpu3.
193and output the statistics gathered after the command exits. 252We add a counter showing the 32-bit raw value of MSR 0x199 (MSR_IA32_PERF_CTL),
194In this case, turbostat output goes to stderr, by default. 253labeling it with the column header, "PRF_CTRL", and display it only once,
195Output can instead be saved to a file using the --out option. 254afte the conclusion of a 0.1 second sleep.
196eg. Here a cycle soaker is run on 1 CPU (see %c0) for a few seconds
197until ^C while the other CPUs are mostly idle:
198
199.nf 255.nf
200root@hsw: turbostat cat /dev/zero > /dev/null 256sudo ./turbostat --quiet --cpu 0-3 --show CPU --add msr0x199,u32,raw,PRF_CTRL sleep .1
201^C 2570.101604 sec
202 CPU Avg_MHz Busy% Bzy_MHz TSC_MHz 258CPU PRF_CTRL
203 - 482 12.51 3854 3498 259- 0x00000000
204 0 0 0.01 1960 3498 2600 0x00000c00
205 4 0 0.00 2128 3498 2611 0x00000800
206 1 0 0.00 3003 3498 2622 0x00000a00
207 5 3854 99.98 3855 3498 2633 0x00000800
208 2 0 0.01 3504 3498
209 6 3 0.08 3884 3498
210 3 0 0.00 2553 3498
211 7 0 0.00 2126 3498
21210.783983 sec
213 264
214.fi 265.fi
215Above the cycle soaker drives cpu5 up its 3.9 GHz turbo limit.
216The first row shows the average MHz and Busy% across all the processors in the system.
217
218Note that the Avg_MHz column reflects the total number of cycles executed
219divided by the measurement interval. If the Busy% column is 100%,
220then the processor was running at that speed the entire interval.
221The Avg_MHz multiplied by the Busy% results in the Bzy_MHz --
222which is the average frequency while the processor was executing --
223not including any non-busy idle time.
224 266
225.SH NOTES 267.SH NOTES
226 268