Lines Matching refs:t

36   event hits.  If 'values' isn't specified, an implicit 'hitcount'
87   Note that in general the semantics of a given field aren't
92       are essentially sums, and the other modifiers don't make sense
99       values wouldn't be correct, and typically events that care save
194   they were actual event fields, but aren't really part of the event's
309   which wasn't specified in the trigger.  Also notice that in the
311   wasn't specified in the trigger either.  The reason for that is that
319   the 'values' parameter if you don't really need to have any
330   isn't really very useful.  It's an address, but normally addresses
802   don't really care about at the moment.  Since we know the syscall
898   In this example, we'll aggregate fork counts and don't expect a
1487   any two events even if they don't share any 'compatible' fields
1652   - A histogram consisting of inter-event quantities isn't logically a
1654     event host the histogram output doesn't really make sense).  To
1667   - Trace events don't have a 'timestamp' associated with them, but
1671     histograms as if it were any other event field; it isn't an actual
1680 bogus timestamp differences with other clocks that aren't coherent
1701 it's reset to its 'unset' state, which means it can't be used again
1702 unless it's set again.  This ensures not only that an event doesn't
1732 If a variable isn't a key variable or prefixed with 'vals=', the
1733 associated event field will be saved in a variable but won't be summed
1846 At this point, there isn't yet an actual 'wakeup_latency' event
2118 if a given handler.action combination isn't supported, the hist
2571  # ./cyclictest -p80 -d0 -i250 -n -a -t --tracemark -b 1000
2578  -t    : one thread per available CPU
3069 This doesn't tell us any information about how late cyclictest may have