Lines Matching refs:record
16 Trace data is collected by 'perf record' and stored within the perf.data file.
17 See below for options to 'perf record'.
52 Data is captured with 'perf record' e.g. to trace 'ls' userspace-only:
54 perf record -e intel_pt//u ls
67 ~/libexec/perf-core/perf-with-kcore record pt_ls -e intel_pt// -- ls
94 perf record -e intel_pt//u ls
125 perf record
264 $ perf record -e intel_pt/psb_period=15/u uname
281 packets. MTC packets record time using the hardware crystal
316 $ perf record -e intel_pt/mtc_period=15/u uname
362 $ perf record -e intel_pt/cyc,cyc_thresh=15/u uname
439 perf record -e intel_pt//u uname
443 perf record -v -e intel_pt//u -S ./loopy 1000000000 &
482 By default "perf record" post-processes the event stream to find all build ids
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
635 [ perf record: Woken up 1 times to write data ]
636 [ perf record: Captured and wrote 0.042 MB perf.data ]
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"
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 ]