Lines Matching full:cyc

154 If the 'cyc' config term (see <<_config_terms,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
317 	-e intel_pt/cyc/
322 	-e intel_pt/cyc=1/
331 	-e intel_pt/cyc,mtc_period=9/
394 of MTC or CYC.
442 *cyc*::
443 Produces CYC timing packets.
445 CYC packets provide even finer grain timestamp information than
446 MTC and TSC packets.  A CYC packet contains the number of CPU
447 cycles since the last CYC packet. Unlike MTC and TSC packets,
448 CYC packets are only sent when another packet is also sent.
457 The number of CYC packets produced can be reduced by specifying
461 Specifies how frequently CYC packets are produced - see cyc
462 above for how to determine if CYC packets are supported.
472 that must have passed before a CYC packet can be sent.  The
477 e.g. value 4 means 8 CPU cycles must pass before a CYC packet
478 can be sent.  Note a CYC packet is still only sent when another
484 	$ perf record -e intel_pt/cyc,cyc_thresh=15/u uname
487 CYC packets are not requested by default.
991 (ie., the default). Note that even with CYC packets enabled and no sampling,
992 these are not fully accurate, since CYC packets are not emitted for each
1355 However, IPC can still be determined, hence cyc=1 can be added.
1360 …st --host --guestkallsyms $KALLSYMS record --kcore -e intel_pt/tsc=0,mtc=0,cyc=1/k -p 1430 --per-t…
1418 IPC can be determined, hence cyc=1 can be added.
1422 …$ sudo perf kvm --guest --host --guestkallsyms $KALLSYMS record --kcore -e intel_pt/cyc=1/k -p 169…
1524  $ sudo perf record -o guest-sideband-testing-host-perf.data -m,64M --kcore -a -e intel_pt/cyc/
1678 …# perf record --kcore -e intel_pt/cyc/ -- tools/testing/selftests/kselftest_install/kvm/tsc_msrs_t…