Lines Matching full:cyc

154 If the 'cyc' config term (see config terms section below) was used, then IPC
155 and cycle events are calculated using the cycle count from CYC packets, otherwise
166 Even with the 'cyc' config term, it is possible to produce IPC information for
184 presently sampled, so IPC values for them do not appear e.g. a CYC packet with a
250 	/sys/bus/event_source/devices/intel_pt/format/cyc:config:1
373 		of MTC or CYC.
419 cyc		Produces CYC timing packets.
421 		CYC packets provide even finer grain timestamp information than
422 		MTC and TSC packets.  A CYC packet contains the number of CPU
423 		cycles since the last CYC packet. Unlike MTC and TSC packets,
424 		CYC packets are only sent when another packet is also sent.
433 		The number of CYC packets produced can be reduced by specifying
436 cyc_thresh	Specifies how frequently CYC packets are produced - see cyc
437 		above for how to determine if CYC packets are supported.
447 		that must have passed before a CYC packet can be sent.  The
452 		e.g. value 4 means 8 CPU cycles must pass before a CYC packet
453 		can be sent.  Note a CYC packet is still only sent when another
459 			$ perf record -e intel_pt/cyc,cyc_thresh=15/u uname
462 		CYC packets are not requested by default.
937 (ie., the default). Note that even with CYC packets enabled and no sampling,
938 these are not fully accurate, since CYC packets are not emitted for each
1301 However, IPC can still be determined, hence cyc=1 can be added.
1306 …st --host --guestkallsyms $KALLSYMS record --kcore -e intel_pt/tsc=0,mtc=0,cyc=1/k -p 1430 --per-t…
1364 IPC can be determined, hence cyc=1 can be added.
1368 …$ sudo perf kvm --guest --host --guestkallsyms $KALLSYMS record --kcore -e intel_pt/cyc=1/k -p 169…
1470  $ sudo perf record -o guest-sideband-testing-host-perf.data -m,64M --kcore -a -e intel_pt/cyc/
1624 …# perf record --kcore -e intel_pt/cyc/ -- tools/testing/selftests/kselftest_install/kvm/tsc_msrs_t…