Lines Matching refs:trace

20 the trace data packets. For example a TNT packet only tells whether a
38 A limitation of Intel PT is that it produces huge amounts of trace data
52 Data is captured with 'perf record' e.g. to trace 'ls' userspace-only:
60 To also trace kernel space presents a problem, namely kernel self-modifying
100 	perf script -Fcomm,tid,pid,time,cpu,event,trace,ip,sym,dso,addr,symoff,flags
103 system, asynchronous, interrupt, transaction abort, trace begin, trace end, and
255 		trace bytes between PSB packets as:
371 The difference between full trace and snapshot from the kernel's perspective is
372 that in full trace we don't overwrite trace data that the user hasn't collected
374 the trace run and overwrite older data in the buffer so that whenever something
420 In full-trace mode, powers of two are allowed for buffer size, with a minimum
434 	full-trace mode
437 Full-trace mode traces continuously e.g.
464 	becomes full and some trace data is lost.
468 If trace data is lost, the driver sets 'truncated' in the PERF_RECORD_AUX event
471 In full-trace mode, the driver waits for data to be copied out before allowing
542 Inheritance is allowed.  Note that you can now trace a workload in per-thread
643 cannot be matched against the Intel PT trace.
649 By default, perf script will decode trace data found in the perf.data file.
686 Error events are new.  They show where the decoder lost the trace.  Error events
699 microseconds of trace.  Alternatives to "us" are "ms" (milliseconds),
731 To disable trace decoding entirely, use the option --no-itrace.
745 in the buffer might be truncated and immediately followed by a PSB as the trace
755 By default, perf report will decode trace data found in the perf.data file.