Documentation/trace/events.rst

13 using the event tracing infrastructure.
15 Not all tracepoints can be traced using the event tracing system;
169 combined using the logical operators '&&' and '||'.  A predicate is
222 Cpumask fields or scalar fields that encode a CPU number can be filtered using
313 Set a filter using only common fields for all events in the sched
323 Attempt to set a filter using a non-common field for all events in the
414 For ease of use, writing to the trigger file using '>' currently just
614 The first creates the event in one step, using synth_event_create().
646 to the event, using dynamic arrays implies that the piecewise
664 first be created using synth_event_gen_cmd_start() or
672 initialize a dynevent_cmd object using synth_event_cmd_init().
690 Alternatively, using an array of struct synth_field_desc fields
697 populated with more fields.  Fields are added one by one using
707 A group of fields can also be added all at once using an array of
729 option is to trace the event in one call, using synth_event_trace()
744 representing the synthetic event (which can be retrieved using
745 trace_get_event_file() using the synthetic event name, "synthetic" as
746 the system name, and the trace instance name (NULL if using the global
764 the event for the string, using these pointers.
768 representing the synthetic event (which can be retrieved using
769 trace_get_event_file() using the synthetic event name, "synthetic" as
770 the system name, and the trace instance name (NULL if using the global
793 the event for the string, using these pointers.
828 trace instance should be 'put' back using trace_put_event_file()::
842 To trace a synthetic using the piecewise method described above, the
851 using the same methods as described above, along with a pointer to a
868 in order.  The same sequence of calls as in the above examples using
896 the above examples using this method would be (without error-handling
914 which is done using synth_event_trace_end(), which takes only the
931 should first be created using kprobe_event_gen_cmd_start().  The name
935 should create and initialize a dynevent_cmd object using
957 populated with more fields.  Fields can be added using
978 Similarly, a kretprobe event can be created using
1018 using the dynevent_create() function.  The details of the interface
1059 The arg object is first initialized using dynevent_arg_init() and in
1064 Here's another more complicated example using an 'arg pair', which is