Lines Matching refs:function

32 the entry to a kernel function, and provides convenient access to the
33 function's arguments.  A return probe fires when a specified function
37 a kernel module.  The module's init function installs ("registers")
38 one or more probes, and the exit function unregisters them.  A
39 registration function such as register_kprobe() specifies where
80 A jprobe is implemented using a kprobe that is placed on a function's
82 seamless access to the probed function's arguments.  The jprobe
84 type) as the function being probed, and must always end by calling
85 the Kprobes function jprobe_return().
92 stack contents as the probed function.  When it is done, the handler
94 contents and processor state and switch to the probed function.
102 Note that the probed function's args may be passed on the stack
104 handler's prototype matches that of the probed function.
111 the entry to the function.  When the probed function is called and this
117 When the probed function executes its return instruction, control
123 While the probed function is executing, its return address is
127 function can be probed simultaneously.  register_kretprobe()
130 For example, if the function is non-recursive and is called with a
131 spinlock held, maxactive = 1 should be enough.  If the function is
140 time the probed function is entered but there is no kretprobe_instance
146 on function entry. This handler is specified by setting the entry_handler
148 function entry is hit, the user-defined entry_handler, if any, is invoked.
150 is guaranteed to be called upon function return. If the entry_handler
152 the kretprobe has no further effect for that particular function instance.
163 In case probed function is entered but there is no kretprobe_instance
187 instruction (the "optimized region") lies entirely within one function.
191 - Kprobes analyzes the entire function and verifies that there is no
193   - the function contains no indirect jump;
194   - the function contains no instruction that causes an exception (since
273 - Specify an empty function for the kprobe's post_handler or break_handler.
284 If you want to add a function into the blacklist, you just need
286 to specify a blacklisted function.
319 If you need to insert a probe in the middle of a function, you may find
326 The Kprobes API includes a "register" function and an "unregister"
327 function for each type of probe. The API also includes "register_*probes"
354 (64-bit powerpc intricacies such as function descriptors are handled
404 of the first instruction of a function.  When the breakpoint is hit,
408 function; and just before it returns, it must call jprobe_return().
410 control to Kprobes.)  If the probed function is declared asmlinkage
421 Establishes a return probe for the function whose address is
422 rp->kp.addr.  When that function returns, Kprobes calls rp->handler.
456 Removes the specified probe.  The unregister function can be called
473 function returns.
519 however, there cannot be multiple jprobes on the same function at
534 If you install a probe in an inline-able function, Kprobes makes
535 no attempt to chase down all inline instances of the function and
536 install probes there.  gcc may inline a function without being asked,
539 A probe handler can modify the environment of the probed function
573 If the number of times a function is called does not match the number
574 of times it returns, registering a return probe on that function may
582 If, upon entry to or exit from a function, the CPU is running on
584 probe on that function may produce undesirable results.  For this
628 When you have a return probe set on a function, adding a kprobe at
629 the entry to that function adds essentially no overhead.
633 on same function; jr = jprobe + return probe on same function
699 the probe. If the probed function belongs to a module, the module name