Lines Matching refs:with

36 with an exclamation point:
104 Each trace event has a 'format' file associated with it that contains
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
114 the fields prefixed with 'common_'.  The other fields vary between
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
160 values don't match will be discarded.  An event with no filter
161 associated with it matches everything, and is the default when no
170 logged event with a constant value and returns either 0 or 1 depending
220 argument' error when setting it, and the erroneous string along with
271 subsystem (all events end up with the same filter):
298 with attached triggers is invoked, the set of trigger commands
299 associated with that event is invoked.  Any given trigger can
301 section 5 (Event filtering) associated with it - the command will only
303 If no filter is associated with the trigger, it always passes.
308 A given event can have any number of triggers associated with it,
313 whenever a trace event has one or more triggers associated with it,
334 Triggers are removed by echoing the same command but starting with '!'
412   request happens with a size >= 64K
444   queue is unplugged with a depth > 1.  If you were tracing a set of
474   request queue is unplugged with a depth > 1.  If you were tracing a