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
168 Following those are the 'event handler' functions generated one for
169 every event in the 'perf record' output.  The handler functions take
178 doesn't correspond to any event handler in the script.  This could
232 sys_enter() handler do the necessary tallying until all events have
234 store that information; every time the sys_enter() handler is called,
258 Putting that code into the raw_syscalls__sys_enter() handler, we
269 handler called at the end of script processing.
420 That will generate a starter script containing a handler for each of
434 'handler function' is called for each event in the trace.  If there's
435 no handler function defined for a given event type, the event is
440 handler function; some of the less common ones aren't - those are
468 The handler function for this event would be defined as:
477 The handler function takes the form subsystem__event_name.
479 The common_* arguments in the handler's argument list are the set of
496 counterparts as handler function arguments of the same name, as can be
521 The rest of the script can contain handler functions and support
524 Aside from the event handler functions discussed above, every script
545  doesn't have a handler explicitly defined for it.  The standard set
595 context variable passed into every event handler as the second