Lines Matching refs:PT

16 Intel Processor Trace (Intel PT) is an extension of Intel Architecture that
22 Intel PT is first supported in Intel Core M and 5th generation Intel Core
39 The main distinguishing feature of Intel PT is that the decoder can determine
40 the exact flow of software execution.  Intel PT can be used to understand why
42 software does not have to be recompiled, so Intel PT works with debug or release
47 A limitation of Intel PT is that it produces huge amounts of trace data
60 The simplest thing to do with Intel PT is userspace profiling of small programs.
94 Also note that the coarseness of Intel PT timing information will start to
159 Because Intel PT does not update the cycle count on every branch or instruction,
210 Refer to 'new snapshot option' and 'Intel PT modes of operation' further below.
228 The Intel PT kernel driver creates a new PMU for Intel PT.  PMU events are
283 'h', 'G' and 'H' are for virtualization which are not used by Intel PT.
284 'p' is also not relevant to Intel PT.  So only options 'u' and 'k' are
285 meaningful for Intel PT.
315 Manuals, Chapter 36 Intel Processor Trace, defined new Intel PT features.
530 To select Intel PT "sampling" the AUX area sampling option can be used:
538 In addition, the Intel PT event to sample must be defined e.g.
542 Samples on other events will be created containing Intel PT data e.g. the
543 following will create Intel PT samples on the branch-misses event, note the
564 	Intel PT sample size (%zu) may be too small for PSB period (%zu)
603 	Intel PT snapshot size: %zu
609 Intel PT buffer size is specified by an addition to the -m option e.g.
618 The default auxtrace mmap size for Intel PT is 4MiB/page_size for privileged users
639 Intel PT modes of operation
642 Intel PT can be used in 3 modes:
651 Sample mode attaches a Intel PT sample to other events e.g.
683 The 3 Intel PT modes of operation cannot be used together.
710 Intel PT and build ids
714 for executables for all addresses sampled.  Deliberately, Intel PT is not
723 If the perf.data file contains Intel PT data, that is the same as:
798 information to decode Intel PT in per-cpu mode, and potentially workload-only
803 be possible to decode Intel PT in per-cpu mode.
809 The sched_switch tracepoint is used to provide side-band data for Intel PT
889 cannot be matched against the Intel PT trace.
920 	o	synthesize PEBS-via-PT events
992 of code with Intel PT, it is useful to know if a timing bubble was caused
993 by Intel PT or not.
999 The flags supported by Intel PT are:
1012 must be preceded by either '+' or '-'. The flags support by Intel PT are:
1034 The timing information included with Intel PT does not give the time of every
1039 For Intel PT, the default period is 100us.
1043 In the case of Intel PT that is the same as a period of 1 and a unit of
1064 'ls' and then add a call chain derived from the Intel PT trace:
1076 late timestamps.  Because the Intel PT trace is synchronized by timestamps,
1089 Because Intel PT sample mode uses a different sample type to the list above,
1090 Large PEBS is not used with Intel PT sample mode. To avoid Large PEBS in other
1173 When -D is used, Intel PT packets are displayed.  The packet decoder does not
1181 To disable the display of Intel PT packets, combine the -D option with
1201 Below is an example of using Intel PT with autofdo.  It requires autofdo
1227 Note there is currently no advantage to using Intel PT instead of LBR, but
1231 PEBS via Intel PT
1234 Some hardware has the feature to redirect PEBS records to the Intel PT trace.
1242 To check for the presence of that event in a PEBS-via-PT trace:
1246 To display PEBS events from the Intel PT trace, use the itrace 'o' option e.g.
1303 Intel PT traces both the host and the guest so --guest and --host need to be specified.
1366 Intel PT traces both the host and the guest so --guest and --host need to be specified.
1372 Now 'perf inject' can be used to determine the VMX TCS Offset. Note, Intel PT TSC packets are
1441 …ecord to record sideband events within a virtual machine, so that an Intel PT trace on the host ca…
1466 Start perf record to collect Intel PT trace:
1481 Stop the Intel PT trace:
1489 Stop the Intel PT trace:
1509 Correct Intel PT TSC timestamps for the guest machine:
1842 Pipe mode is a problem for Intel PT and possibly other auxtrace users.
1843 It's not recommended to use a pipe as data output with Intel PT because
1851 In the Intel PT case, the head and tail are updated only when the trace