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,
112 data captured is to use 'snapshot' mode which is explained further below.
118 which results in the decoder not knowing what code was executed.
141 which is the same as
148 fields within the config member of the struct perf_event_attr which is
186 'h', 'G' and 'H' are for virtualization which is not supported by Intel PT.
244 		which contains "1" if the feature is supported and "0"
251 		which contains a hexadecimal value, the bits of which represent
282 		clock (CTC) which is related to TSC packets using a TMA packet.
288 		which contains "1" if the feature is supported and
301 		which contains a hexadecimal value, the bits of which represent
310 		Where CTC is the hardware crystal clock, the frequency of which
333 		which contains "1" if the feature is supported and
346 		which contains a hexadecimal value, the bits of which represent
417 their mlock limit (which defaults to 64KiB but is not multiplied by the number
458 There may be buffer limitations (i.e. single ToPa entry) which means that actual
469 which the tools report as an error.
554 not permitted to use tracepoints which means there is insufficient side-band
660 which, in turn, is the same as
763 perf inject also accepts the --itrace option in which case tracing data is