perf/Documentation/perf-intel-pt.txt

11 'perf record' -e intel_pt//
63 	perf record -e intel_pt//u ls
75 	sudo perf record -o pt_ls --kcore -e intel_pt// -- ls
103 	perf record -e intel_pt//u ls
228 	-e intel_pt//
232 	-e intel_pt/tsc,noretcomp=0/
236 	-e intel_pt/tsc=1,noretcomp=0/
240 The config terms are listed in /sys/devices/intel_pt/format.  They are bit
245 	$ grep -H . /sys/bus/event_source/devices/intel_pt/format/*
246 	/sys/bus/event_source/devices/intel_pt/format/cyc:config:1
247 	/sys/bus/event_source/devices/intel_pt/format/cyc_thresh:config:19-22
248 	/sys/bus/event_source/devices/intel_pt/format/mtc:config:9
249 	/sys/bus/event_source/devices/intel_pt/format/mtc_period:config:14-17
250 	/sys/bus/event_source/devices/intel_pt/format/noretcomp:config:11
251 	/sys/bus/event_source/devices/intel_pt/format/psb_period:config:24-27
252 	/sys/bus/event_source/devices/intel_pt/format/tsc:config:10
256 	-e intel_pt/noretcomp=0/
260 	-e intel_pt/tsc=1,noretcomp=0/
264 	-e intel_pt/tsc=0/
268 	-e intel_pt/config=0x400/
335 			/sys/bus/event_source/devices/intel_pt/caps/psb_cyc
342 			/sys/bus/event_source/devices/intel_pt/caps/psb_periods
357 			$ perf record -e intel_pt/psb_period=15/u uname
358 			Invalid psb_period for intel_pt. Valid values are: 0-5
379 			/sys/bus/event_source/devices/intel_pt/caps/mtc
392 			/sys/bus/event_source/devices/intel_pt/caps/mtc_periods
409 			$ perf record -e intel_pt/mtc_period=15/u uname
410 			Invalid mtc_period for intel_pt. Valid values are: 0,3,6,9
424 			/sys/bus/event_source/devices/intel_pt/caps/psb_cyc
437 			/sys/bus/event_source/devices/intel_pt/caps/cycle_thresholds
455 			$ perf record -e intel_pt/cyc,cyc_thresh=15/u uname
456 			Invalid cyc_thresh for intel_pt. Valid values are: 0-12
475 			/sys/bus/event_source/devices/intel_pt/caps/ptwrite
493 			/sys/bus/event_source/devices/intel_pt/caps/power_event_trace
503 			/sys/bus/event_source/devices/intel_pt/caps/event_trace
517 			/sys/bus/event_source/devices/intel_pt/caps/tnt_disable
536 	-e intel_pt//u
542 	perf record --aux-sample -e '{intel_pt//u,branch-misses:u}'
547 	perf record -e intel_pt//u -e branch-misses/aux-sample-size=8192/u
551 	perf record -e '{intel_pt//u,branch-misses/aux-sample-size=8192/u}'
555 …perf record -e intel_pt//u --filter 'filter * @/bin/ls' -e branch-misses/aux-sample-size=8192/u --…
645 	perf record -e intel_pt//u uname
649 	perf record --aux-sample -e intel_pt//u -e branch-misses:u
654 	perf record -v -e intel_pt//u -S ./loopy 1000000000 &
670 	$ sudo ~/bin/perf record --control fifo:perf.control,perf.ack -S -e intel_pt//u -- sleep 60 &
701 wait, the intel_pt event gets disabled.  Because it is difficult to know when
702 that happens, perf tools always re-enable the intel_pt event after copying out
727 In order to make a snapshot, the intel_pt event is disabled using an IOCTL,
731 continue to be recorded while intel_pt is disabled.  That is important to ensure
812 	$ perf record -vv -e intel_pt//u uname
1004 The "d" option will cause the creation of a file "intel_pt.log" containing all
1013 		+o	Output to stdout instead of "intel_pt.log"
1062 	perf record --aux-sample -e '{intel_pt//u,branch-misses:u}' -- ls
1211 	$ perf record -e intel_pt//u ./sort 3000
1233 	perf record -c 10000 -e '{intel_pt/branch=0/,cycles/aux-output/ppp}' uname
1302 …$ sudo perf kvm --guest --host --guestkallsyms $KALLSYMS record --kcore -e intel_pt/tsc=0,mtc=0,cy…
1364 …$ sudo perf kvm --guest --host --guestkallsyms $KALLSYMS record --kcore -e intel_pt/cyc=1/k -p 169…
1396 Note it is also possible to get a intel_pt.log file by adding option --itrace=d
1466  $ sudo perf record -o guest-sideband-testing-host-perf.data -m,64M --kcore -a -e intel_pt/cyc/
1620 …# perf record --kcore -e intel_pt/cyc/ -- tools/testing/selftests/kselftest_install/kvm/tsc_msrs_t…
1700 /sys/bus/event_source/devices/intel_pt/caps/event_trace file.
1704 	perf record -e intel_pt/event/u uname
1744 	perf record -e intel_pt/notnt/u uname
1828  $ perf record -e intel_pt//u ./eg_ptw 0x1234567890abcdef