Lines Matching refs:functions

189 	has a side effect of enabling or disabling specific functions
190 	to be traced. Echoing names of functions into this file
191 	will limit the trace to only those functions.
215 	This lists the functions that ftrace
227 	displays all functions that have a callback attached to them
229 	Note, a callback may also call multiple functions which will
244 	When set it will enable all functions with either the function
246 	keep a histogram of the number of functions that were called
248 	track of the time spent in those functions. The histogram
311 	functions the stack tracer will check.
489 	Function call tracer to trace all kernel functions.
494 	function tracer probes the functions on their entry
496 	and exit of the functions. It then provides the ability
643 The start and stop (the functions in which the interrupts were
788 	       of functions. This allows for back traces of
848   	       time to call nested functions. When this is not set,
851 	       for functions that it called.
891 	    functions. This keeps the overhead of the tracer down
1044 functions that were called during that time. Note that by
1175 an interrupt 'h'. Before that, the functions being traced still
1177 functions themselves that this is not the case.
1990   given on each entry/exit of functions
2020 enabled for functions whose start is in the trace buffer,
2041 You can put some comments on specific functions by using
2057 functions or tasks.
2088 unloaded, it also removes its functions from the ftrace function
2111 One special side-effect to the recording of the functions being
2112 traced is that we can now selectively choose which functions we
2117 tracing of specified functions. They are:
2125 A list of available functions that you can add to these files is
2164 To see which functions are being traced, you can cat the file:
2174   <match>*  - will match functions that begin with <match>
2175   *<match>  - will match functions that end with <match>
2176   *<match>* - will match functions that have <match> in it
2235 To clear out a filter so that all functions will be recorded
2268 The set_ftrace_notrace prevents those functions from being
2352 You can also expand several functions at once:
2357 Now if you want to go back to trace all functions you can clear
2398   functions in the ext3 module are desired, run:
2403   filtering based on function names. Thus, adding more functions
2405   filter file. Remove specific module functions by prepending
2412   functions are hit. The parameter determines how many times the
2790 waste it in functions. A kernel developer must be conscience of
2837 Note, if -mfentry is being used by gcc, functions get traced before
2838 they set up the stack frame. This means that leaf level functions