Lines Matching full:function

17 But callbacks to the start of a function can have other use cases. Either
19 how to use ftrace to implement your own function callbacks.
26   The ability to add a callback to almost any function within the
40 To register a function callback, a ftrace_ops is required. This structure
41 is used to tell ftrace what function should be called as the callback
60 .. c:function::  register_ftrace_function(&ops);
64 .. c:function::  unregister_ftrace_function(&ops);
68 .. c:function:: #include <linux/ftrace.h>
82 The callback function
85 The prototype of the callback function is as follows (as of v4.14):
93 	 This is the instruction pointer of the function that is being traced.
94       	 (where the fentry or mcount is within the function)
97 	This is the instruction pointer of the function that called the
98 	the function being traced (where the call of the function occurred).
108 	at the start of the function where ftrace was tracing. Otherwise it
133 	make sure that recursion of the function does not occur. That is,
134 	if a function that is called as a result of the callback's execution
143 	It is OK if another callback traces a function that is called by a
145 	must never trace any function that are called by the callback
154 	the traced function (have another function called instead of the
155 	traced function), it requires setting this flag. This is what live
160 	registered to any given function at a time.
164 	where RCU is "watching". This is required if the callback function
189 	The string that holds the function filter text.
204 To just trace the schedule function:
221 Sometimes more than one function has the same name. To trace just a specific
222 function in this case, ftrace_set_filter_ip() can be used.
229 located in the function. This function is used by perf and kprobes that
236 be called by any function.
248 filter list, and this function does not modify the filter list.