Lines Matching refs:perf
16 Trace data is collected by 'perf record' and stored within the perf.data file.
17 See below for options to 'perf record'.
25 samples output by perf hardware events, for example as though the "instructions"
27 'perf script', 'perf report' and 'perf inject'. See below for more information
52 Data is captured with 'perf record' e.g. to trace 'ls' userspace-only:
54 perf record -e intel_pt//u ls
56 And profiled with 'perf report' e.g.
58 perf report
63 as the data capture. A script perf-with-kcore can do that, but beware that the
64 script makes use of 'sudo' to copy /proc/kcore. If you have perf installed
67 ~/libexec/perf-core/perf-with-kcore record pt_ls -e intel_pt// -- ls
69 which will create a directory named 'pt_ls' and put the perf.data file and
71 'perf report' becomes:
73 ~/libexec/perf-core/perf-with-kcore report pt_ls
78 ~/libexec/perf-core/perf-with-kcore report pt_ls --itrace=i1usge
91 data is available you can use the 'perf script' tool with no parameters, which
94 perf record -e intel_pt//u ls
95 perf script
100 perf script -Fcomm,tid,pid,time,cpu,event,trace,ip,sym,dso,addr,symoff,flags
120 There is also the problem of perf not being able to copy the data fast enough,
125 perf record
264 $ perf record -e intel_pt/psb_period=15/u uname
316 $ perf record -e intel_pt/mtc_period=15/u uname
362 $ perf record -e intel_pt/cyc,cyc_thresh=15/u uname
414 memory as shown in /proc/self/limits). Note that perf does not count the first
439 perf record -e intel_pt//u uname
443 perf record -v -e intel_pt//u -S ./loopy 1000000000 &
475 that happens, perf tools always re-enable the intel_pt event after copying out
482 By default "perf record" post-processes the event stream to find all build ids
486 in the perf.data file.
488 To see buildids included in the perf.data file use the command:
490 perf buildid-list
492 If the perf.data file contains Intel PT data, that is the same as:
494 perf buildid-list --with-hits
510 perf test list
516 perf test 23
520 perf record modes (nothing new here)
523 perf record essentially operates in one of three modes:
570 $ perf record -vv -e intel_pt//u uname
632 perf event ring buffer mmapped per cpu
635 [ perf record: Woken up 1 times to write data ]
636 [ perf record: Captured and wrote 0.042 MB perf.data ]
646 perf script
649 By default, perf script will decode trace data found in the perf.data file.
676 "Instructions" events look like they were recorded by "perf record -e
679 "Branches" events look like they were recorded by "perf record -e branches". "c"
683 'flags' field can be used in perf script to determine whether the event is a
737 perf script has an option (-D) to "dump" the events i.e. display the binary
752 perf report
755 By default, perf report will decode trace data found in the perf.data file.
757 perf script, with the exception that the default is --itrace=igxe.
760 perf inject
763 perf inject also accepts the --itrace option in which case tracing data is
766 perf inject --itrace -i perf.data -o perf.data.new
782 $ perf record -e intel_pt//u ./sort 3000
785 [ perf record: Woken up 2 times to write data ]
786 [ perf record: Captured and wrote 3.939 MB perf.data ]
787 $ perf inject -i perf.data -o inj --itrace=i100usle --strip