Lines Matching refs:handler

25 can trap at almost any kernel code address(*), specifying a handler
40 the probe is to be inserted and what handler is to be called when
65 associated with the kprobe, passing the handler the addresses of the
83 handler routine should have the same signature (arg list and return
90 handler routine, and returns from the trap.  As a result, control
91 passes to the handler, which is presented with the same register and
92 stack contents as the probed function.  When it is done, the handler
99 handler has run.  Up to MAX_STACK_SIZE bytes are copied -- e.g.,
104 handler's prototype matches that of the probed function.
119 handler calls the user-specified return handler associated with the
143 1.3.2 Kretprobe entry-handler
145 Kretprobes also provides an optional user-specified handler which runs
146 on function entry. This handler is specified by setting the entry_handler
149 If the entry_handler returns 0 (success) then a corresponding return handler
154 Multiple entry and return handler invocations are matched using the unique
258 while the interrupt handler is running. When the interrupt
282 fault) or the nested probe handler may never be called.
370 User's pre-handler (kp->pre_handler):
379 User's post-handler (kp->post_handler):
388 User's fault-handler (kp->fault_handler):
405 Kprobes runs the handler whose address is jp->entry.
407 The handler should have the same arg list and return type as the probed
409 (The handler never actually returns, since jprobe_return() returns
411 or anything else that affects how args are passed, the handler's
422 rp->kp.addr.  When that function returns, Kprobes calls rp->handler.
429 User's return-probe handler (rp->handler):
441 	entry-handler" for details.
447 The handler's return value is currently ignored.
539 A probe handler can modify the environment of the probed function
549 probe handler.  If a probe handler hits a probe, that second probe's
554 the same handler) may run concurrently on different CPUs.
563 your handler should not yield the CPU (e.g., by attempting to acquire
625 probepoint repeatedly, firing a simple handler each time, reports 1-2