Lines Matching full:trace

11 Tracepoints (see Documentation/trace/tracepoints.rst) can be used
105 Each trace event has a 'format' file associated with it that contains
107 be used to parse the binary trace stream, and is also the place to
123 where offset is the offset of the field in the trace record and size
156 Trace events can be filtered in the kernel by associating boolean
158 the trace buffer, its fields are checked against the filter expression
160 'match' the filter will appear in the trace output, and an event whose
181 'format' files for trace events (see section 4).
272 effect) trace output.  Only filters that reference just the common
320 Will only trace events for the current task.
331 Trace events can be made to conditionally invoke trigger 'commands'
333 examples would be enabling or disabling other trace events or invoking
334 a stack trace whenever the trace event is hit.  Whenever a trace event
350 whenever a trace event has one or more triggers associated with it,
360 section of Documentation/trace/ftrace.rst), but there are major
365      Writing into trace_marker (See Documentation/trace/ftrace.rst)
400   These commands can enable or disable another trace event whenever
402   the other trace event is activated, but disabled in a "soft" mode.
444   This command dumps a stacktrace in the trace buffer whenever the
487   events or functions at the time, the snapshot trace buffer would
518   trace buffer to see the sequence of events that led up to the
543   more trace event format fields (or stacktrace) and a set of running
544   totals derived from one or more trace event format fields and/or
547   See Documentation/trace/histogram.rst for details and examples.
549 7. In-kernel trace event API
552 In most cases, the command-line interface to trace events is more than
557 application that needs to 'listen' to the trace stream in order to
561 The trace event subsystem provides an in-kernel API allowing modules
563 will, which can be used to either augment the existing trace stream
572 higher-level trace event APIs.
627 trace buffer won't contain unreadable events when the module is
702 To trace a synthetic event, there are several options.  The first
703 option is to trace the event in one call, using synth_event_trace()
714 To trace a synthetic event all at once, the synth_event_trace() or
720 the system name, and the trace instance name (NULL if using the global
721 trace array)), along with an variable number of u64 args, one for each
724 So, to trace an event corresponding to the synthetic event definition
744 the system name, and the trace instance name (NULL if using the global
745 trace array)), along with an array of u64, one for each synthetic
748 To trace an event corresponding to the synthetic event definition
769 In order to trace a synthetic event, a pointer to the trace event file
771 it - it will find the file in the given trace instance (in this case
772 NULL since the top trace array is being used) while at the same time
779 the synthetic event won't actually show up in the trace buffer.
795 Finally, synth_event_trace_array() can be used to actually trace the
796 event, which should be visible in the trace buffer afterwards::
802 trace instance should be 'put' back using trace_put_event_file()::
816 To trace a synthetic using the piecewise method described above, the
818 event trace::
830 reserved in the trace buffer, the individual fields can be set.  There
884 incompatible if used within the same trace of an event - either one
900 To create a kprobe or kretprobe trace event from kernel code, the
983 layer that can be used to generate trace event commands.  The
985 and event creation code that already exists in the trace event
986 subystem for creating the corresponding trace events.