Lines Matching refs:handler

109 callback handler for each event type found in the perf.data trace
122 # The common_* event handler fields are the most useful fields common to
124 # in the format files.  Those fields not available as handler params can
170 Following those are the 'event handler' functions generated one for
171 every event in the 'perf record' output.  The handler functions take
180 doesn't correspond to any event handler in the script.  This could
234 sys_enter() handler do the necessary tallying until all events have
236 store that information; every time the sys_enter() handler is called,
260 Putting that code into the raw_syscalls__sys_enter() handler, we
271 handler called at the end of script processing.
424 That will generate a starter script containing a handler for each of
438 'handler function' is called for each event in the trace.  If there's
439 no handler function defined for a given event type, the event is
444 handler function; some of the less common ones aren't - those are
472 The handler function for this event would be defined as:
481 The handler function takes the form subsystem__event_name.
483 The common_* arguments in the handler's argument list are the set of
500 counterparts as handler function arguments of the same name, as can be
525 The rest of the script can contain handler functions and support
528 Aside from the event handler functions discussed above, every script
549  doesn't have a handler explicitly defined for it.  The standard set
600 context variable passed into every event handler as the second