Lines Matching refs:packets
18 modes and timings and formats it into highly compressed binary packets.
29 the trace data packets. For example a TNT packet only tells whether a
151 calculated using the cycle count from CYC packets, otherwise MTC packets are
242 So, to disable TSC packets use:
295 tsc Always supported. Produces TSC timestamp packets to provide
303 is produced when a function returns. Causes more packets to be
308 psb_period Allows the frequency of PSB packets to be specified.
328 trace bytes between PSB packets as:
340 If MTC packets are selected, the default config selects a value
351 mtc Produces MTC timing packets.
353 MTC packets provide finer grain timestamp information than TSC
354 packets. MTC packets record time using the hardware crystal
355 clock (CTC) which is related to TSC packets using a TMA packet.
364 The frequency of MTC packets can also be specified - see
367 mtc_period Specifies how frequently MTC packets are produced - see mtc
368 above for how to determine if MTC packets are supported.
395 cyc Produces CYC timing packets.
397 CYC packets provide even finer grain timestamp information than
398 MTC and TSC packets. A CYC packet contains the number of CPU
399 cycles since the last CYC packet. Unlike MTC and TSC packets,
400 CYC packets are only sent when another packet is also sent.
409 The number of CYC packets produced can be reduced by specifying
412 cyc_thresh Specifies how frequently CYC packets are produced - see cyc
413 above for how to determine if CYC packets are supported.
438 CYC packets are not requested by default.
450 ptw Enable PTWRITE packets which are produced when a ptwrite instruction
488 notnt Disable TNT packets. Without TNT packets, it is not possible to walk
490 and TIP.PGD packets still indicate asynchronous control flow, and (if
492 The advantage of eliminating TNT packets is reducing the size of the
863 Note also, the sched_switch event is only added if TSC packets are requested.
918 flow packets which can be disabled by using the config term "branch=0". Refer
922 "fup_on_ptw" was used. "ptwrite" events depend on PTWRITE packets which are
928 "Power" events correspond to power event packets and CBR (core-to-bus ratio)
929 packets. While CBR packets are always recorded when tracing is enabled, power
930 event packets are recorded only if the "pwr_evt" config term was used. Refer to
967 decoded packets and instructions. Note that this option slows down the decoder
1057 decode TNT packets, and does not walk object code, but gets the ip from FUP and
1058 TIP packets. The q option can be used with the b and i options but the period
1061 TIP.PGD packets (refer below). However the q option could be used to find time
1079 - instruction pointer associated with PSB packets
1085 less detail. The decoder decodes only extended PSB (PSB+) packets, getting the
1087 PSBEND). Note PSB packets occur regularly in the trace based on the psb_period
1093 - everything except instruction pointer associated with PSB packets
1097 - instruction pointer associated with PSB packets
1110 When -D is used, Intel PT packets are displayed. The packet decoder does not
1111 pay attention to PSB packets, but just decodes the bytes - so the packets seen
1118 To disable the display of Intel PT packets, combine the -D option with
1197 VMX controls may suppress packets needed for decoding resulting in decoding errors
1304 Now 'perf inject' can be used to determine the VMX TCS Offset. Note, Intel PT TSC packets are
1374 faults, VM exits and entries. The information is recorded in CFE and EVD packets,
1435 TNT packets are disabled using the "notnt" config term. e.g.
1450 a trace that encodes the payload data into TNT packets. Here is an example