Lines Matching full:using

13 using the event tracing infrastructure.
15 Not all tracepoints can be traced using the event tracing system;
20 2. Using Event Tracing
193 combined using the logical operators '&&' and '||'.  A predicate is
246 Cpumask fields or scalar fields that encode a CPU number can be filtered using
337 Set a filter using only common fields for all events in the sched
347 Attempt to set a filter using a non-common field for all events in the
438 For ease of use, writing to the trigger file using '>' currently just
638 The first creates the event in one step, using synth_event_create().
670 to the event, using dynamic arrays implies that the piecewise
688 first be created using synth_event_gen_cmd_start() or
696 initialize a dynevent_cmd object using synth_event_cmd_init().
714 Alternatively, using an array of struct synth_field_desc fields
721 populated with more fields.  Fields are added one by one using
731 A group of fields can also be added all at once using an array of
753 option is to trace the event in one call, using synth_event_trace()
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
788 the event for the string, using these pointers.
792 representing the synthetic event (which can be retrieved using
793 trace_get_event_file() using the synthetic event name, "synthetic" as
794 the system name, and the trace instance name (NULL if using the global
817 the event for the string, using these pointers.
852 trace instance should be 'put' back using trace_put_event_file()::
866 To trace a synthetic using the piecewise method described above, the
875 using the same methods as described above, along with a pointer to a
892 in order.  The same sequence of calls as in the above examples using
920 the above examples using this method would be (without error-handling
938 which is done using synth_event_trace_end(), which takes only the
955 should first be created using kprobe_event_gen_cmd_start().  The name
959 should create and initialize a dynevent_cmd object using
981 populated with more fields.  Fields can be added using
1002 Similarly, a kretprobe event can be created using
1042 using the dynevent_create() function.  The details of the interface
1083 The arg object is first initialized using dynevent_arg_init() and in
1088 Here's another more complicated example using an 'arg pair', which is