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.
221 	This lists the functions that ftrace
233 	displays all functions that have a callback attached to them
235 	Note, a callback may also call multiple functions which will
250 	When set it will enable all functions with either the function
252 	keep a histogram of the number of functions that were called
254 	track of the time spent in those functions. The histogram
317 	functions the stack tracer will check.
500 	Function call tracer to trace all kernel functions.
505 	function tracer probes the functions on their entry
507 	and exit of the functions. It then provides the ability
654 The start and stop (the functions in which the interrupts were
801 	       of functions. This allows for back traces of
861   	       time to call nested functions. When this is not set,
864 	       for functions that it called.
904 	    functions. This keeps the overhead of the tracer down
1057 functions that were called during that time. Note that by
1188 an interrupt 'h'. Before that, the functions being traced still
1190 functions themselves that this is not the case.
2026   given on each entry/exit of functions
2056 enabled for functions whose start is in the trace buffer,
2077 You can put some comments on specific functions by using
2093 functions or tasks.
2124 unloaded, it also removes its functions from the ftrace function
2147 One special side-effect to the recording of the functions being
2148 traced is that we can now selectively choose which functions we
2153 tracing of specified functions. They are:
2161 A list of available functions that you can add to these files is
2200 To see which functions are being traced, you can cat the file:
2210   <match>*  - will match functions that begin with <match>
2211   *<match>  - will match functions that end with <match>
2212   *<match>* - will match functions that have <match> in it
2271 To clear out a filter so that all functions will be recorded
2304 The set_ftrace_notrace prevents those functions from being
2388 You can also expand several functions at once:
2393 Now if you want to go back to trace all functions you can clear
2434   functions in the ext3 module are desired, run:
2439   filtering based on function names. Thus, adding more functions
2441   filter file. Remove specific module functions by prepending
2447   functions except a specific module:
2465   functions are hit. The parameter determines how many times the
2843 waste it in functions. A kernel developer must be conscience of
2890 Note, if -mfentry is being used by gcc, functions get traced before
2891 they set up the stack frame. This means that leaf level functions