Lines Matching refs:which
19 Trace data must be 'decoded' which involves walking the object code and matching
22 decoder must know precisely which instruction was being executed.
34 builds, however the executed images are needed - which makes use in JIT-compiled
39 (hundreds of megabytes per second per core) which takes a long time to decode,
69 which will create a directory named 'pt_ls' and put the perf.data file and
91 data is available you can use the 'perf script' tool with no parameters, which
97 An interesting field that is not printed by default is 'flags' which can be
102 The flags are "bcrosyiABEx" which stand for branch, call, return, conditional,
111 There is also script intel-pt-events.py which provides an example of how to
115 data captured is to use 'snapshot' mode which is explained further below.
121 which results in the decoder not knowing what code was executed.
144 which is the same as
151 fields within the config member of the struct perf_event_attr which is
189 'h', 'G' and 'H' are for virtualization which is not supported by Intel PT.
247 which contains "1" if the feature is supported and "0"
254 which contains a hexadecimal value, the bits of which represent
285 clock (CTC) which is related to TSC packets using a TMA packet.
291 which contains "1" if the feature is supported and
304 which contains a hexadecimal value, the bits of which represent
313 Where CTC is the hardware crystal clock, the frequency of which
336 which contains "1" if the feature is supported and
349 which contains a hexadecimal value, the bits of which represent
370 pt Specifies pass-through which enables the 'branch' config term.
380 ptw Enable PTWRITE packets which are produced when a ptwrite instruction
387 which contains "1" if the feature is supported and
403 which contains "1" if the feature is supported and
456 their mlock limit (which defaults to 64KiB but is not multiplied by the number
497 There may be buffer limitations (i.e. single ToPa entry) which means that actual
508 which the tools report as an error.
593 PERF_RECORD_SWITCH, which allows unprivileged users to see when their processes
594 are scheduled out and in, just not by whom, which is left for the
596 which in turn requires CAP_SYS_ADMIN.
605 not permitted to use tracepoints which means there is insufficient side-band
714 which, in turn, is the same as
744 flow packets which can be disabled by using the config term "branch=0". Refer
748 "fup_on_ptw" was used. "ptwrite" events depend on PTWRITE packets which are
859 perf inject also accepts the --itrace option in which case tracing data is