1 1
2 Performance Counters for Linux 2 Performance Counters for Linux
3 ------------------------------ 3 ------------------------------
4 4
5 Performance counters are special hardware regi 5 Performance counters are special hardware registers available on most modern
6 CPUs. These registers count the number of cert 6 CPUs. These registers count the number of certain types of hw events: such
7 as instructions executed, cachemisses suffered 7 as instructions executed, cachemisses suffered, or branches mis-predicted -
8 without slowing down the kernel or application 8 without slowing down the kernel or applications. These registers can also
9 trigger interrupts when a threshold number of 9 trigger interrupts when a threshold number of events have passed - and can
10 thus be used to profile the code that runs on 10 thus be used to profile the code that runs on that CPU.
11 11
12 The Linux Performance Counter subsystem provid 12 The Linux Performance Counter subsystem provides an abstraction of these
13 hardware capabilities. It provides per task an 13 hardware capabilities. It provides per task and per CPU counters, counter
14 groups, and it provides event capabilities on 14 groups, and it provides event capabilities on top of those. It
15 provides "virtual" 64-bit counters, regardless 15 provides "virtual" 64-bit counters, regardless of the width of the
16 underlying hardware counters. 16 underlying hardware counters.
17 17
18 Performance counters are accessed via special 18 Performance counters are accessed via special file descriptors.
19 There's one file descriptor per virtual counte 19 There's one file descriptor per virtual counter used.
20 20
21 The special file descriptor is opened via the !! 21 The special file descriptor is opened via the perf_event_open()
22 system call: 22 system call:
23 23
24 int sys_perf_event_open(struct perf_event_a !! 24 int sys_perf_event_open(struct perf_event_hw_event *hw_event_uptr,
25 pid_t pid, int cp 25 pid_t pid, int cpu, int group_fd,
26 unsigned long fla 26 unsigned long flags);
27 27
28 The syscall returns the new fd. The fd can be 28 The syscall returns the new fd. The fd can be used via the normal
29 VFS system calls: read() can be used to read t 29 VFS system calls: read() can be used to read the counter, fcntl()
30 can be used to set the blocking mode, etc. 30 can be used to set the blocking mode, etc.
31 31
32 Multiple counters can be kept open at a time, 32 Multiple counters can be kept open at a time, and the counters
33 can be poll()ed. 33 can be poll()ed.
34 34
35 When creating a new counter fd, 'perf_event_at !! 35 When creating a new counter fd, 'perf_event_hw_event' is:
36 36
37 struct perf_event_attr { !! 37 struct perf_event_hw_event {
38 /* 38 /*
39 * The MSB of the config word signifie 39 * The MSB of the config word signifies if the rest contains cpu
40 * specific (raw) counter configuratio 40 * specific (raw) counter configuration data, if unset, the next
41 * 7 bits are an event type and the re 41 * 7 bits are an event type and the rest of the bits are the event
42 * identifier. 42 * identifier.
43 */ 43 */
44 __u64 config; 44 __u64 config;
45 45
46 __u64 irq_period; 46 __u64 irq_period;
47 __u32 record_type; 47 __u32 record_type;
48 __u32 read_format; 48 __u32 read_format;
49 49
50 __u64 disabled 50 __u64 disabled : 1, /* off by default */
51 inherit 51 inherit : 1, /* children inherit it */
52 pinned 52 pinned : 1, /* must always be on PMU */
53 exclusive 53 exclusive : 1, /* only group on PMU */
54 exclude_user 54 exclude_user : 1, /* don't count user */
55 exclude_kernel 55 exclude_kernel : 1, /* ditto kernel */
56 exclude_hv 56 exclude_hv : 1, /* ditto hypervisor */
57 exclude_idle 57 exclude_idle : 1, /* don't count when idle */
58 mmap 58 mmap : 1, /* include mmap data */
59 munmap 59 munmap : 1, /* include munmap data */
60 comm 60 comm : 1, /* include comm data */
61 61
62 __reserved_1 62 __reserved_1 : 52;
63 63
64 __u32 extra_config_l 64 __u32 extra_config_len;
65 __u32 wakeup_events; 65 __u32 wakeup_events; /* wakeup every n events */
66 66
67 __u64 __reserved_2; 67 __u64 __reserved_2;
68 __u64 __reserved_3; 68 __u64 __reserved_3;
69 }; 69 };
70 70
71 The 'config' field specifies what the counter 71 The 'config' field specifies what the counter should count. It
72 is divided into 3 bit-fields: 72 is divided into 3 bit-fields:
73 73
74 raw_type: 1 bit (most significant bit) 74 raw_type: 1 bit (most significant bit) 0x8000_0000_0000_0000
75 type: 7 bits (next most significant) 75 type: 7 bits (next most significant) 0x7f00_0000_0000_0000
76 event_id: 56 bits (least significant) 76 event_id: 56 bits (least significant) 0x00ff_ffff_ffff_ffff
77 77
78 If 'raw_type' is 1, then the counter will coun 78 If 'raw_type' is 1, then the counter will count a hardware event
79 specified by the remaining 63 bits of event_co 79 specified by the remaining 63 bits of event_config. The encoding is
80 machine-specific. 80 machine-specific.
81 81
82 If 'raw_type' is 0, then the 'type' field says 82 If 'raw_type' is 0, then the 'type' field says what kind of counter
83 this is, with the following encoding: 83 this is, with the following encoding:
84 84
85 enum perf_type_id { !! 85 enum perf_event_types {
86 PERF_TYPE_HARDWARE = 0, 86 PERF_TYPE_HARDWARE = 0,
87 PERF_TYPE_SOFTWARE = 1, 87 PERF_TYPE_SOFTWARE = 1,
88 PERF_TYPE_TRACEPOINT = 2, 88 PERF_TYPE_TRACEPOINT = 2,
89 }; 89 };
90 90
91 A counter of PERF_TYPE_HARDWARE will count the 91 A counter of PERF_TYPE_HARDWARE will count the hardware event
92 specified by 'event_id': 92 specified by 'event_id':
93 93
94 /* 94 /*
95 * Generalized performance counter event types 95 * Generalized performance counter event types, used by the hw_event.event_id
96 * parameter of the sys_perf_event_open() sysc 96 * parameter of the sys_perf_event_open() syscall:
97 */ 97 */
98 enum perf_hw_id { !! 98 enum hw_event_ids {
99 /* 99 /*
100 * Common hardware events, generalized 100 * Common hardware events, generalized by the kernel:
101 */ 101 */
102 PERF_COUNT_HW_CPU_CYCLES 102 PERF_COUNT_HW_CPU_CYCLES = 0,
103 PERF_COUNT_HW_INSTRUCTIONS 103 PERF_COUNT_HW_INSTRUCTIONS = 1,
104 PERF_COUNT_HW_CACHE_REFERENCES !! 104 PERF_COUNT_HW_CACHE_REFERENCES = 2,
105 PERF_COUNT_HW_CACHE_MISSES 105 PERF_COUNT_HW_CACHE_MISSES = 3,
106 PERF_COUNT_HW_BRANCH_INSTRUCTIONS 106 PERF_COUNT_HW_BRANCH_INSTRUCTIONS = 4,
107 PERF_COUNT_HW_BRANCH_MISSES !! 107 PERF_COUNT_HW_BRANCH_MISSES = 5,
108 PERF_COUNT_HW_BUS_CYCLES 108 PERF_COUNT_HW_BUS_CYCLES = 6,
109 PERF_COUNT_HW_STALLED_CYCLES_FRONTEND <<
110 PERF_COUNT_HW_STALLED_CYCLES_BACKEND <<
111 PERF_COUNT_HW_REF_CPU_CYCLES <<
112 }; 109 };
113 110
114 These are standardized types of events that wo 111 These are standardized types of events that work relatively uniformly
115 on all CPUs that implement Performance Counter 112 on all CPUs that implement Performance Counters support under Linux,
116 although there may be variations (e.g., differ 113 although there may be variations (e.g., different CPUs might count
117 cache references and misses at different level 114 cache references and misses at different levels of the cache hierarchy).
118 If a CPU is not able to count the selected eve 115 If a CPU is not able to count the selected event, then the system call
119 will return -EINVAL. 116 will return -EINVAL.
120 117
121 More hw_event_types are supported as well, but 118 More hw_event_types are supported as well, but they are CPU-specific
122 and accessed as raw events. For example, to c 119 and accessed as raw events. For example, to count "External bus
123 cycles while bus lock signal asserted" events 120 cycles while bus lock signal asserted" events on Intel Core CPUs, pass
124 in a 0x4064 event_id value and set hw_event.ra 121 in a 0x4064 event_id value and set hw_event.raw_type to 1.
125 122
126 A counter of type PERF_TYPE_SOFTWARE will coun 123 A counter of type PERF_TYPE_SOFTWARE will count one of the available
127 software events, selected by 'event_id': 124 software events, selected by 'event_id':
128 125
129 /* 126 /*
130 * Special "software" counters provided by the 127 * Special "software" counters provided by the kernel, even if the hardware
131 * does not support performance counters. Thes 128 * does not support performance counters. These counters measure various
132 * physical and sw events of the kernel (and a 129 * physical and sw events of the kernel (and allow the profiling of them as
133 * well): 130 * well):
134 */ 131 */
135 enum perf_sw_ids { !! 132 enum sw_event_ids {
136 PERF_COUNT_SW_CPU_CLOCK = 0, 133 PERF_COUNT_SW_CPU_CLOCK = 0,
137 PERF_COUNT_SW_TASK_CLOCK = 1, !! 134 PERF_COUNT_SW_TASK_CLOCK = 1,
138 PERF_COUNT_SW_PAGE_FAULTS = 2, !! 135 PERF_COUNT_SW_PAGE_FAULTS = 2,
139 PERF_COUNT_SW_CONTEXT_SWITCHES = 3, 136 PERF_COUNT_SW_CONTEXT_SWITCHES = 3,
140 PERF_COUNT_SW_CPU_MIGRATIONS = 4, 137 PERF_COUNT_SW_CPU_MIGRATIONS = 4,
141 PERF_COUNT_SW_PAGE_FAULTS_MIN = 5, 138 PERF_COUNT_SW_PAGE_FAULTS_MIN = 5,
142 PERF_COUNT_SW_PAGE_FAULTS_MAJ = 6, 139 PERF_COUNT_SW_PAGE_FAULTS_MAJ = 6,
143 PERF_COUNT_SW_ALIGNMENT_FAULTS = 7, <<
144 PERF_COUNT_SW_EMULATION_FAULTS = 8, <<
145 }; 140 };
146 141
147 Counters of the type PERF_TYPE_TRACEPOINT are 142 Counters of the type PERF_TYPE_TRACEPOINT are available when the ftrace event
148 tracer is available, and event_id values can b 143 tracer is available, and event_id values can be obtained from
149 /debug/tracing/events/*/*/id 144 /debug/tracing/events/*/*/id
150 145
151 146
152 Counters come in two flavours: counting counte 147 Counters come in two flavours: counting counters and sampling
153 counters. A "counting" counter is one that is 148 counters. A "counting" counter is one that is used for counting the
154 number of events that occur, and is characteri 149 number of events that occur, and is characterised by having
155 irq_period = 0. 150 irq_period = 0.
156 151
157 152
158 A read() on a counter returns the current valu 153 A read() on a counter returns the current value of the counter and possible
159 additional values as specified by 'read_format 154 additional values as specified by 'read_format', each value is a u64 (8 bytes)
160 in size. 155 in size.
161 156
162 /* 157 /*
163 * Bits that can be set in hw_event.read_forma 158 * Bits that can be set in hw_event.read_format to request that
164 * reads on the counter should return the indi 159 * reads on the counter should return the indicated quantities,
165 * in increasing order of bit value, after the 160 * in increasing order of bit value, after the counter value.
166 */ 161 */
167 enum perf_event_read_format { 162 enum perf_event_read_format {
168 PERF_FORMAT_TOTAL_TIME_ENABLED = 1, 163 PERF_FORMAT_TOTAL_TIME_ENABLED = 1,
169 PERF_FORMAT_TOTAL_TIME_RUNNING = 2, 164 PERF_FORMAT_TOTAL_TIME_RUNNING = 2,
170 }; 165 };
171 166
172 Using these additional values one can establis 167 Using these additional values one can establish the overcommit ratio for a
173 particular counter allowing one to take the ro 168 particular counter allowing one to take the round-robin scheduling effect
174 into account. 169 into account.
175 170
176 171
177 A "sampling" counter is one that is set up to 172 A "sampling" counter is one that is set up to generate an interrupt
178 every N events, where N is given by 'irq_perio 173 every N events, where N is given by 'irq_period'. A sampling counter
179 has irq_period > 0. The record_type controls w 174 has irq_period > 0. The record_type controls what data is recorded on each
180 interrupt: 175 interrupt:
181 176
182 /* 177 /*
183 * Bits that can be set in hw_event.record_typ 178 * Bits that can be set in hw_event.record_type to request information
184 * in the overflow packets. 179 * in the overflow packets.
185 */ 180 */
186 enum perf_event_record_format { 181 enum perf_event_record_format {
187 PERF_RECORD_IP = 1U << 0, 182 PERF_RECORD_IP = 1U << 0,
188 PERF_RECORD_TID = 1U << 1, 183 PERF_RECORD_TID = 1U << 1,
189 PERF_RECORD_TIME = 1U << 2, 184 PERF_RECORD_TIME = 1U << 2,
190 PERF_RECORD_ADDR = 1U << 3, 185 PERF_RECORD_ADDR = 1U << 3,
191 PERF_RECORD_GROUP = 1U << 4, 186 PERF_RECORD_GROUP = 1U << 4,
192 PERF_RECORD_CALLCHAIN = 1U << 5, 187 PERF_RECORD_CALLCHAIN = 1U << 5,
193 }; 188 };
194 189
195 Such (and other) events will be recorded in a 190 Such (and other) events will be recorded in a ring-buffer, which is
196 available to user-space using mmap() (see belo 191 available to user-space using mmap() (see below).
197 192
198 The 'disabled' bit specifies whether the count 193 The 'disabled' bit specifies whether the counter starts out disabled
199 or enabled. If it is initially disabled, it c 194 or enabled. If it is initially disabled, it can be enabled by ioctl
200 or prctl (see below). 195 or prctl (see below).
201 196
202 The 'inherit' bit, if set, specifies that this 197 The 'inherit' bit, if set, specifies that this counter should count
203 events on descendant tasks as well as the task 198 events on descendant tasks as well as the task specified. This only
204 applies to new descendents, not to any existin 199 applies to new descendents, not to any existing descendents at the
205 time the counter is created (nor to any new de 200 time the counter is created (nor to any new descendents of existing
206 descendents). 201 descendents).
207 202
208 The 'pinned' bit, if set, specifies that the c 203 The 'pinned' bit, if set, specifies that the counter should always be
209 on the CPU if at all possible. It only applie 204 on the CPU if at all possible. It only applies to hardware counters
210 and only to group leaders. If a pinned counte 205 and only to group leaders. If a pinned counter cannot be put onto the
211 CPU (e.g. because there are not enough hardwar 206 CPU (e.g. because there are not enough hardware counters or because of
212 a conflict with some other event), then the co 207 a conflict with some other event), then the counter goes into an
213 'error' state, where reads return end-of-file 208 'error' state, where reads return end-of-file (i.e. read() returns 0)
214 until the counter is subsequently enabled or d 209 until the counter is subsequently enabled or disabled.
215 210
216 The 'exclusive' bit, if set, specifies that wh 211 The 'exclusive' bit, if set, specifies that when this counter's group
217 is on the CPU, it should be the only group usi 212 is on the CPU, it should be the only group using the CPU's counters.
218 In future, this will allow sophisticated monit 213 In future, this will allow sophisticated monitoring programs to supply
219 extra configuration information via 'extra_con 214 extra configuration information via 'extra_config_len' to exploit
220 advanced features of the CPU's Performance Mon 215 advanced features of the CPU's Performance Monitor Unit (PMU) that are
221 not otherwise accessible and that might disrup 216 not otherwise accessible and that might disrupt other hardware
222 counters. 217 counters.
223 218
224 The 'exclude_user', 'exclude_kernel' and 'excl 219 The 'exclude_user', 'exclude_kernel' and 'exclude_hv' bits provide a
225 way to request that counting of events be rest 220 way to request that counting of events be restricted to times when the
226 CPU is in user, kernel and/or hypervisor mode. 221 CPU is in user, kernel and/or hypervisor mode.
227 222
228 Furthermore the 'exclude_host' and 'exclude_gu <<
229 to request counting of events restricted to gu <<
230 using Linux as the hypervisor. <<
231 <<
232 The 'mmap' and 'munmap' bits allow recording o 223 The 'mmap' and 'munmap' bits allow recording of PROT_EXEC mmap/munmap
233 operations, these can be used to relate usersp 224 operations, these can be used to relate userspace IP addresses to actual
234 code, even after the mapping (or even the whol 225 code, even after the mapping (or even the whole process) is gone,
235 these events are recorded in the ring-buffer ( 226 these events are recorded in the ring-buffer (see below).
236 227
237 The 'comm' bit allows tracking of process comm 228 The 'comm' bit allows tracking of process comm data on process creation.
238 This too is recorded in the ring-buffer (see b 229 This too is recorded in the ring-buffer (see below).
239 230
240 The 'pid' parameter to the sys_perf_event_open !! 231 The 'pid' parameter to the perf_event_open() system call allows the
241 counter to be specific to a task: 232 counter to be specific to a task:
242 233
243 pid == 0: if the pid parameter is zero, the c 234 pid == 0: if the pid parameter is zero, the counter is attached to the
244 current task. 235 current task.
245 236
246 pid > 0: the counter is attached to a specifi 237 pid > 0: the counter is attached to a specific task (if the current task
247 has sufficient privilege to do so) 238 has sufficient privilege to do so)
248 239
249 pid < 0: all tasks are counted (per cpu count 240 pid < 0: all tasks are counted (per cpu counters)
250 241
251 The 'cpu' parameter allows a counter to be mad 242 The 'cpu' parameter allows a counter to be made specific to a CPU:
252 243
253 cpu >= 0: the counter is restricted to a spec 244 cpu >= 0: the counter is restricted to a specific CPU
254 cpu == -1: the counter counts on all CPUs 245 cpu == -1: the counter counts on all CPUs
255 246
256 (Note: the combination of 'pid == -1' and 'cpu 247 (Note: the combination of 'pid == -1' and 'cpu == -1' is not valid.)
257 248
258 A 'pid > 0' and 'cpu == -1' counter is a per t 249 A 'pid > 0' and 'cpu == -1' counter is a per task counter that counts
259 events of that task and 'follows' that task to 250 events of that task and 'follows' that task to whatever CPU the task
260 gets schedule to. Per task counters can be cre 251 gets schedule to. Per task counters can be created by any user, for
261 their own tasks. 252 their own tasks.
262 253
263 A 'pid == -1' and 'cpu == x' counter is a per 254 A 'pid == -1' and 'cpu == x' counter is a per CPU counter that counts
264 all events on CPU-x. Per CPU counters need CAP !! 255 all events on CPU-x. Per CPU counters need CAP_SYS_ADMIN privilege.
265 privilege. <<
266 256
267 The 'flags' parameter is currently unused and 257 The 'flags' parameter is currently unused and must be zero.
268 258
269 The 'group_fd' parameter allows counter "group 259 The 'group_fd' parameter allows counter "groups" to be set up. A
270 counter group has one counter which is the gro 260 counter group has one counter which is the group "leader". The leader
271 is created first, with group_fd = -1 in the sy !! 261 is created first, with group_fd = -1 in the perf_event_open call
272 that creates it. The rest of the group member 262 that creates it. The rest of the group members are created
273 subsequently, with group_fd giving the fd of t 263 subsequently, with group_fd giving the fd of the group leader.
274 (A single counter on its own is created with g 264 (A single counter on its own is created with group_fd = -1 and is
275 considered to be a group with only 1 member.) 265 considered to be a group with only 1 member.)
276 266
277 A counter group is scheduled onto the CPU as a 267 A counter group is scheduled onto the CPU as a unit, that is, it will
278 only be put onto the CPU if all of the counter 268 only be put onto the CPU if all of the counters in the group can be
279 put onto the CPU. This means that the values 269 put onto the CPU. This means that the values of the member counters
280 can be meaningfully compared, added, divided ( 270 can be meaningfully compared, added, divided (to get ratios), etc.,
281 with each other, since they have counted event 271 with each other, since they have counted events for the same set of
282 executed instructions. 272 executed instructions.
283 273
284 274
285 Like stated, asynchronous events, like counter 275 Like stated, asynchronous events, like counter overflow or PROT_EXEC mmap
286 tracking are logged into a ring-buffer. This r 276 tracking are logged into a ring-buffer. This ring-buffer is created and
287 accessed through mmap(). 277 accessed through mmap().
288 278
289 The mmap size should be 1+2^n pages, where the 279 The mmap size should be 1+2^n pages, where the first page is a meta-data page
290 (struct perf_event_mmap_page) that contains va 280 (struct perf_event_mmap_page) that contains various bits of information such
291 as where the ring-buffer head is. 281 as where the ring-buffer head is.
292 282
293 /* 283 /*
294 * Structure of the page that can be mapped vi 284 * Structure of the page that can be mapped via mmap
295 */ 285 */
296 struct perf_event_mmap_page { 286 struct perf_event_mmap_page {
297 __u32 version; /* ver 287 __u32 version; /* version number of this structure */
298 __u32 compat_version; /* low 288 __u32 compat_version; /* lowest version this is compat with */
299 289
300 /* 290 /*
301 * Bits needed to read the hw counters 291 * Bits needed to read the hw counters in user-space.
302 * 292 *
303 * u32 seq; 293 * u32 seq;
304 * s64 count; 294 * s64 count;
305 * 295 *
306 * do { 296 * do {
307 * seq = pc->lock; 297 * seq = pc->lock;
308 * 298 *
309 * barrier() 299 * barrier()
310 * if (pc->index) { 300 * if (pc->index) {
311 * count = pmc_read(pc->index - 301 * count = pmc_read(pc->index - 1);
312 * count += pc->offset; 302 * count += pc->offset;
313 * } else 303 * } else
314 * goto regular_read; 304 * goto regular_read;
315 * 305 *
316 * barrier(); 306 * barrier();
317 * } while (pc->lock != seq); 307 * } while (pc->lock != seq);
318 * 308 *
319 * NOTE: for obvious reason this only 309 * NOTE: for obvious reason this only works on self-monitoring
320 * processes. 310 * processes.
321 */ 311 */
322 __u32 lock; /* seq 312 __u32 lock; /* seqlock for synchronization */
323 __u32 index; /* har 313 __u32 index; /* hardware counter identifier */
324 __s64 offset; /* add 314 __s64 offset; /* add to hardware counter value */
325 315
326 /* 316 /*
327 * Control data for the mmap() data bu 317 * Control data for the mmap() data buffer.
328 * 318 *
329 * User-space reading this value shoul 319 * User-space reading this value should issue an rmb(), on SMP capable
330 * platforms, after reading this value 320 * platforms, after reading this value -- see perf_event_wakeup().
331 */ 321 */
332 __u32 data_head; /* hea 322 __u32 data_head; /* head in the data section */
333 }; 323 };
334 324
335 NOTE: the hw-counter userspace bits are arch s 325 NOTE: the hw-counter userspace bits are arch specific and are currently only
336 implemented on powerpc. 326 implemented on powerpc.
337 327
338 The following 2^n pages are the ring-buffer wh 328 The following 2^n pages are the ring-buffer which contains events of the form:
339 329
340 #define PERF_RECORD_MISC_KERNEL (1 << 330 #define PERF_RECORD_MISC_KERNEL (1 << 0)
341 #define PERF_RECORD_MISC_USER (1 << 331 #define PERF_RECORD_MISC_USER (1 << 1)
342 #define PERF_RECORD_MISC_OVERFLOW (1 << 332 #define PERF_RECORD_MISC_OVERFLOW (1 << 2)
343 333
344 struct perf_event_header { 334 struct perf_event_header {
345 __u32 type; 335 __u32 type;
346 __u16 misc; 336 __u16 misc;
347 __u16 size; 337 __u16 size;
348 }; 338 };
349 339
350 enum perf_event_type { 340 enum perf_event_type {
351 341
352 /* 342 /*
353 * The MMAP events record the PROT_EXE 343 * The MMAP events record the PROT_EXEC mappings so that we can
354 * correlate userspace IPs to code. Th 344 * correlate userspace IPs to code. They have the following structure:
355 * 345 *
356 * struct { 346 * struct {
357 * struct perf_event_header 347 * struct perf_event_header header;
358 * 348 *
359 * u32 349 * u32 pid, tid;
360 * u64 350 * u64 addr;
361 * u64 351 * u64 len;
362 * u64 352 * u64 pgoff;
363 * char 353 * char filename[];
364 * }; 354 * };
365 */ 355 */
366 PERF_RECORD_MMAP = 1, 356 PERF_RECORD_MMAP = 1,
367 PERF_RECORD_MUNMAP = 2, 357 PERF_RECORD_MUNMAP = 2,
368 358
369 /* 359 /*
370 * struct { 360 * struct {
371 * struct perf_event_header 361 * struct perf_event_header header;
372 * 362 *
373 * u32 363 * u32 pid, tid;
374 * char 364 * char comm[];
375 * }; 365 * };
376 */ 366 */
377 PERF_RECORD_COMM = 3, 367 PERF_RECORD_COMM = 3,
378 368
379 /* 369 /*
380 * When header.misc & PERF_RECORD_MISC 370 * When header.misc & PERF_RECORD_MISC_OVERFLOW the event_type field
381 * will be PERF_RECORD_* 371 * will be PERF_RECORD_*
382 * 372 *
383 * struct { 373 * struct {
384 * struct perf_event_header 374 * struct perf_event_header header;
385 * 375 *
386 * { u64 ip; 376 * { u64 ip; } && PERF_RECORD_IP
387 * { u32 pid, t 377 * { u32 pid, tid; } && PERF_RECORD_TID
388 * { u64 time; 378 * { u64 time; } && PERF_RECORD_TIME
389 * { u64 addr; 379 * { u64 addr; } && PERF_RECORD_ADDR
390 * 380 *
391 * { u64 nr; 381 * { u64 nr;
392 * { u64 event, val; } cnt[nr 382 * { u64 event, val; } cnt[nr]; } && PERF_RECORD_GROUP
393 * 383 *
394 * { u16 nr, 384 * { u16 nr,
395 * hv, 385 * hv,
396 * kernel 386 * kernel,
397 * user; 387 * user;
398 * u64 ips[nr 388 * u64 ips[nr]; } && PERF_RECORD_CALLCHAIN
399 * }; 389 * };
400 */ 390 */
401 }; 391 };
402 392
403 NOTE: PERF_RECORD_CALLCHAIN is arch specific a 393 NOTE: PERF_RECORD_CALLCHAIN is arch specific and currently only implemented
404 on x86. 394 on x86.
405 395
406 Notification of new events is possible through 396 Notification of new events is possible through poll()/select()/epoll() and
407 fcntl() managing signals. 397 fcntl() managing signals.
408 398
409 Normally a notification is generated for every 399 Normally a notification is generated for every page filled, however one can
410 additionally set perf_event_attr.wakeup_events !! 400 additionally set perf_event_hw_event.wakeup_events to generate one every
411 so many counter overflow events. 401 so many counter overflow events.
412 402
413 Future work will include a splice() interface 403 Future work will include a splice() interface to the ring-buffer.
414 404
415 405
416 Counters can be enabled and disabled in two wa 406 Counters can be enabled and disabled in two ways: via ioctl and via
417 prctl. When a counter is disabled, it doesn't 407 prctl. When a counter is disabled, it doesn't count or generate
418 events but does continue to exist and maintain 408 events but does continue to exist and maintain its count value.
419 409
420 An individual counter can be enabled with !! 410 An individual counter or counter group can be enabled with
421 411
422 ioctl(fd, PERF_EVENT_IOC_ENABLE, 0); !! 412 ioctl(fd, PERF_EVENT_IOC_ENABLE);
423 413
424 or disabled with 414 or disabled with
425 415
426 ioctl(fd, PERF_EVENT_IOC_DISABLE, 0); !! 416 ioctl(fd, PERF_EVENT_IOC_DISABLE);
427 417
428 For a counter group, pass PERF_IOC_FLAG_GROUP <<
429 Enabling or disabling the leader of a group en 418 Enabling or disabling the leader of a group enables or disables the
430 whole group; that is, while the group leader i 419 whole group; that is, while the group leader is disabled, none of the
431 counters in the group will count. Enabling or 420 counters in the group will count. Enabling or disabling a member of a
432 group other than the leader only affects that 421 group other than the leader only affects that counter - disabling an
433 non-leader stops that counter from counting bu 422 non-leader stops that counter from counting but doesn't affect any
434 other counter. 423 other counter.
435 424
436 Additionally, non-inherited overflow counters 425 Additionally, non-inherited overflow counters can use
437 426
438 ioctl(fd, PERF_EVENT_IOC_REFRESH, nr); 427 ioctl(fd, PERF_EVENT_IOC_REFRESH, nr);
439 428
440 to enable a counter for 'nr' events, after whi 429 to enable a counter for 'nr' events, after which it gets disabled again.
441 430
442 A process can enable or disable all the counte 431 A process can enable or disable all the counter groups that are
443 attached to it, using prctl: 432 attached to it, using prctl:
444 433
445 prctl(PR_TASK_PERF_EVENTS_ENABLE); 434 prctl(PR_TASK_PERF_EVENTS_ENABLE);
446 435
447 prctl(PR_TASK_PERF_EVENTS_DISABLE); 436 prctl(PR_TASK_PERF_EVENTS_DISABLE);
448 437
449 This applies to all counters on the current pr 438 This applies to all counters on the current process, whether created
450 by this process or by another, and doesn't aff 439 by this process or by another, and doesn't affect any counters that
451 this process has created on other processes. 440 this process has created on other processes. It only enables or
452 disables the group leaders, not any other memb 441 disables the group leaders, not any other members in the groups.
453 442
454 443
455 Arch requirements 444 Arch requirements
456 ----------------- 445 -----------------
457 446
458 If your architecture does not have hardware pe 447 If your architecture does not have hardware performance metrics, you can
459 still use the generic software counters based 448 still use the generic software counters based on hrtimers for sampling.
460 449
461 So to start with, in order to add HAVE_PERF_EV 450 So to start with, in order to add HAVE_PERF_EVENTS to your Kconfig, you
462 will need at least this: 451 will need at least this:
463 - asm/perf_event.h - a basic stub will 452 - asm/perf_event.h - a basic stub will suffice at first
464 - support for atomic64 types (and asso 453 - support for atomic64 types (and associated helper functions)
>> 454 - set_perf_event_pending() implemented
465 455
466 If your architecture does have hardware capabi 456 If your architecture does have hardware capabilities, you can override the
467 weak stub hw_perf_event_init() to register har 457 weak stub hw_perf_event_init() to register hardware counters.
468 458
469 Architectures that have d-cache aliassing issu 459 Architectures that have d-cache aliassing issues, such as Sparc and ARM,
470 should select PERF_USE_VMALLOC in order to avo 460 should select PERF_USE_VMALLOC in order to avoid these for perf mmap().
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.