Lines Matching refs:record

75 that, but first we need to record the data that will be processed by
92 don't care how it exited, so we'll use 'perf record' to record only
96 # perf record -a -e raw_syscalls:sys_enter
98 ^C[ perf record: Woken up 1 times to write data ]
99 [ perf record: Captured and wrote 56.545 MB perf.data (~2470503 samples) ]
171 every event in the 'perf record' output.  The handler functions take
181 mean either that the record step recorded event types that it wasn't
325 detailed event and field info, record the corresponding trace data
326 using 'perf record', passing it the list of interesting events,
345 probably lengthy 'perf record' command needed to record the events for
351 The 'record' script is a shell script with the same base name as your
352 script, but with -record appended.  The shell script should be put
354 In that script, you write the 'perf record' command-line needed for
358 # cat kernel-source/tools/perf/scripts/python/bin/syscall-counts-record
361 perf record -a -e raw_syscalls:sys_enter
410 You can now perform the record step via 'perf script record':
412   # perf script record syscall-counts
447 As an example, the following perf record command can be used to record
450  # perf record -a -e sched:sched_wakeup