Lines Matching refs:event

11 using the event tracing infrastructure.
13 Not all tracepoints can be traced using the event tracing system;
27 To enable a particular event, such as 'sched_wakeup', simply echo it
35 To disable an event, echo the event name to the set_event file prefixed
49 etc., and a full event name looks like this: <subsystem>:<event>.  The
63 To enable event 'sched_wakeup':
84  ? - this file does not affect any event
91 	trace_event=[event-list]
93 event-list is a comma separated list of events. See section 2.1 for event
96 3. Defining an event-enabled tracepoint
104 Each trace event has a 'format' file associated with it that contains
105 a description of each field in a logged event.  This information can
107 find the field names that can be used in event filters (see section 5).
110 event in text mode, along with the event name and ID used for
113 Every event has a set of 'common' fields associated with it; these are
116 definition for that event.
126 event:
148 This event contains 10 fields, the first 5 common and the remaining 5
149 event-specific.  All the fields for this event are numeric, except for
150 'comm' which is a string, a distinction important for event filtering.
156 'filter expressions' with them.  As soon as an event is logged into
158 associated with that event type.  An event with field values that
159 'match' the filter will appear in the trace output, and an event whose
160 values don't match will be discarded.  An event with no filter
162 filter has been set for an event.
170 logged event with a constant value and returns either 0 or 1 depending
206 A filter for an individual event is set by writing a filter expression
207 to the 'filter' file for the given event.
238 To clear the filter for an event, write a '0' to the event's filter
247 For convenience, filters for every event in a subsystem can be set or
250 event within the subsystem lacks a field specified in the subsystem
252 filter for that event will retain its previous setting.  This can
315 a stack trace whenever the trace event is hit.  Whenever a trace event
317 associated with that event is invoked.  Any given trigger can
318 additionally have an event filter of the same form as described in
320 be invoked if the event being invoked passes the associated filter.
323 Triggers are added to and removed from a particular event by writing
324 trigger expressions to the 'trigger' file for the given event.
326 A given event can have any number of triggers associated with it,
331 whenever a trace event has one or more triggers associated with it,
332 the event is activated even if it isn't actually enabled, but is
336 enabled, and also allows the current event filter implementation to be
339 The syntax for event triggers is roughly based on the syntax for
376   These commands can enable or disable another trace event whenever
377   the triggering event is hit.  When these commands are registered,
378   the other trace event is activated, but disabled in a "soft" mode.
380   The event tracepoint stays in this mode as long as there's a trigger
399       enable_event:<system>:<event>[:count]
400       disable_event:<system>:<event>[:count]
411   per triggering event, but there can only be one trigger per
412   triggered event. e.g. sys_enter_read can have triggers enabling both
421   triggering event occurs.
454   event.
459   triggering event occurs.
464   capture those events when the trigger event occurred:
483   event.
495   trigger event:
514   triggering event.