Searched refs:we (Results 1 – 10 of 10) sorted by relevance
| /tools/perf/ |
| D | builtin-timechart.c | 425 struct wake_event *we = zalloc(sizeof(*we)); in sched_wakeup() local
427 if (!we) in sched_wakeup()
430 we->time = timestamp; in sched_wakeup()
431 we->waker = pid; in sched_wakeup()
434 we->waker = -1; in sched_wakeup()
436 we->wakee = wake->pid; in sched_wakeup()
437 we->next = wake_events; in sched_wakeup()
438 wake_events = we; in sched_wakeup()
439 p = find_create_pid(we->wakee); in sched_wakeup()
683 struct wake_event *we; in draw_wakeups() local
[all …]
|
| D | design.txt | 345 * The MMAP events record the PROT_EXEC mappings so that we can
|
| /tools/perf/Documentation/ |
| D | perf-script-python.txt | 75 that, but first we need to record the data that will be processed by
76 that script. Theoretically, there are a couple of ways we could do
79 - we could enable every event under the tracing/events/syscalls
82 useful if we want to later use the guidance we get from the
86 - we can enable the sys_enter and/or sys_exit syscalls found under
91 For this script, we only need to know that a syscall was entered; we
92 don't care how it exited, so we'll use 'perf record' to record only
107 Once we have a perf.data file containing our data, we can use the -g
208 Of course, for this script, we're not interested in printing every
209 trace event, but rather aggregating it in a useful way. So we'll get
[all …]
|
| /tools/perf/tests/attr/ |
| D | README | 10 these files are checked for values we expect for command.
22 separate file. Besides 'struct perf_event_attr' values we also
|
| /tools/virtio/virtio-trace/ |
| D | README | 38 To use this trace agent for virtio-trace, we need to prepare some virtio-serial
|
| /tools/power/cpupower/po/ |
| D | de.po | 246 #. on Intel and AMD, but we assume boost capable machines can do that
|
| D | fr.po | 245 #. on Intel and AMD, but we assume boost capable machines can do that
|
| D | pt.po | 244 #. on Intel and AMD, but we assume boost capable machines can do that
|
| D | cs.po | 250 #. on Intel and AMD, but we assume boost capable machines can do that
|
| D | it.po | 245 #. on Intel and AMD, but we assume boost capable machines can do that
|