Lines Matching full:will
53 option will do) the directory /sys/kernel/tracing will be created. To mount
72 the tracefs file system will be automatically mounted at:
76 All files located in the tracefs file system will be located in that
81 Any selected ftrace option will also create the tracefs file system.
82 The rest of the document will assume that you are in the ftrace directory
83 (cd /sys/kernel/tracing) and will only concentrate on the files within that
89 After mounting tracefs you will have access to the control and output files
117 kernel to disable writing to the ring buffer, which will
121 Note, the function and event trigger "traceoff" will also
131 (no tracer running, or tracing_on is zero), it will produce
140 Reads from this file will block until new data is
145 will not be read again with a sequential read. The
147 adding more data, it will display the same
168 The maximum time is saved in this file. The max trace will also be
169 stored, and displayed by "trace". A new max trace will only be
173 By echoing in a time into this file, no latency will be recorded
178 Some latency tracers will record a trace whenever the
188 will block until the given amount of data specified by buffer_percent
208 than requested, the rest of the page will be used,
215 this file will show "X".
240 data in the ring buffer and the snapshot buffer will be discarded.
247 of this file, the ring buffer will be resized to its minimum size.
249 exits its file descriptor for this file will be closed, and in doing so,
250 the ring buffer will be "freed".
268 will limit the trace to only those functions.
281 written will instead select the same corresponding at the line position
287 set_ftrace_filter. Any function that is added here will not
289 and set_ftrace_notrace, the function will _not_ be traced.
297 PID is listed in this file forks, the child's PID will
298 automatically be added to this file, and the child will be
299 traced by the function tracer as well. This option will also
308 PID is listed in this file forks, the child's PID will
309 automatically be added to this file, and the child will not be
310 traced by the function tracer as well. This option will also
314 file takes precedence, and the thread will not be traced.
319 Note, sched_switch and sched_wake_up will also trace events
323 added on fork, enable the "event-fork" option. That option will also
330 Note, sched_switch and sched_wakeup will trace threads not listed
336 added on fork, enable the "event-fork" option. That option will also
342 Functions listed in this file will cause the function graph
350 Similar to set_graph_function, but will disable function graph
382 Note, a callback may also call multiple functions which will
387 will be displayed on the same line as the function that
392 an 'I' will be displayed on the same line as the function that
395 If a non ftrace trampoline is attached (BPF) a 'D' will be displayed.
401 such cases an 'O' will be displayed.
404 it in the past, a 'M' will be shown. This flag is never cleared. It is
408 If the architecture supports it, it will also show what callback
410 than 1 it most likely will be ftrace_ops_list_func().
414 its address will be printed as well as the function that the
431 When set it will enable all functions with either the function
432 tracer, or if configured, the function graph tracer. It will
434 and if the function graph tracer was configured, it will also keep
455 it will trace into a function. Setting this to a value of
456 one will show only the first kernel function that is called
477 will not be saved during recording. By default, it is enabled.
500 When the stack tracer is activated, this will display the
513 functions the stack tracer will check.
552 Eventually perf will be able to read ftrace buffers
553 and this will help out in interleaving the data.
610 this file will be written into the ftrace buffer.
675 By echoing in the event into this file, will enable that event.
729 This is similar to the "trace" file, but it will only display
736 read, but it will only display (and consume) the data specific
749 reads will always produce different data.
753 This is similar to the main "snapshot" file, but will only
760 Similar to the trace_pipe_raw, but will read the binary format
872 It will trace all the calls that a module makes to the
879 calls within the kernel. It will trace when a likely and
897 support it, reading the tracing/error_log file after an error will
1085 Note, the latency tracers will usually end with a back trace
1151 seeing just "ktime_get", you will see
1159 This will also display the function address as well
1175 This will display raw numbers. This option is best for
1180 Similar to raw, but the numbers will be in a hexadecimal format.
1183 This will print out the formats in raw binary.
1186 When set, reading trace_pipe will not block when polled.
1201 level trace has this set, and will get it set again if another
1215 oldest events). When the annotate option is set, it will
1247 When set, trace_printk()s will only show the format
1261 When set, opening the trace file for read, will pause
1264 When the file is closed, tracing will be enabled again.
1269 This will be useful if you want to find out which hashed
1294 When the free_buffer is closed, tracing will
1314 When disabled, the trace_marker will error with EINVAL
1318 When set, tasks with PIDs listed in set_event_pid will have
1321 their PIDs will be removed from the file.
1326 The latency tracers will enable function tracing
1333 When set, tasks with PIDs listed in set_ftrace_pid will
1336 set_ftrace_pid exit, their PIDs will be removed from the
1342 When set, the latency tracers (irqsoff, wakeup, etc) will
1369 will be critically degraded. Remember to disable
1415 interrupt will not be traced.
1418 When set, the return event will include the function
1425 will be printed after an equal sign "=". By default
1429 When set, the return value will always be printed
1431 the return value is an error code, it will be printed
1432 in signed decimal format; otherwise it will also be
1439 When enabled, it will account time the task has been
1445 not set, the time reported for the function will only
1807 The irqsoff tracer will record the total length of
1811 The preemptoff tracer will record the total length of
1815 But neither will trace the time that interrupts and/or
2051 tracing non-RT tasks that are unpredictable will overwrite the
2055 Since this tracer only deals with RT tasks, we will run this
2057 Instead of performing an 'ls', we will run 'sleep 1' under
2281 NOTE, this tracer will affect the performance of the system as it will
2313 The above output is somewhat the same in the header. All events will have
2342 All architectures that have NMIs will show the "nmi-count" if an
2350 needs to be detected before the trace will be recorded.
2361 runs. That is, the test will run for "width"
2366 runs the test. This thread will alternate between CPUs
2809 it will be printed in signed decimal format, otherwise it will
2830 option, and these limitations will be eliminated in the future:
2832 - Even if the function return type is void, a return value will still
2836 value contained in the first register will be recorded and printed.
2840 will be recorded and printed.
2901 will produce::
2915 If CONFIG_DYNAMIC_FTRACE is set, the system will run with
2919 starts of pointing to a simple return. (Enabling FTRACE will
2924 program will parse the ELF headers in the C object to find all
2938 original object. The final linking stage of the kernel will add all these
3035 will match functions that begin with <match>
3037 will match functions that end with <match>
3039 will match functions that have <match> in it
3041 will match functions that begin with <match1> and end with <match2>
3100 To clear out a filter so that all functions will be recorded
3176 in a list of numbers, no string processing will occur. Instead, the function
3184 Will select the first function listed in "available_filter_functions"
3214 will produce the following "expanded" trace of the __do_fault()
3354 Will cause a snapshot to be triggered when the function is hit.
3373 a "soft" mode. That is, the tracepoint will be called, but
3374 just will not be traced. The event tracepoint stays in this mode
3394 When the function is hit, it will dump the contents of the ftrace
3401 When the function is hit, it will dump the contents of the ftrace
3414 trace_pipe is consumed. This means that subsequent reads will be
3450 Note, reading the trace_pipe file will block until more input is
3452 the trace file for reading, it will actually disable tracing and
3483 It will try to allocate as much as possible. If you allocate too
3499 at the top level will just show an X
3511 Writing to the top level buffer_size_kb will reset all the buffers
3591 one of the latency tracers, you will get the following results.
3606 with mkdir in this directory will already contain files and other
3725 directories, the rmdir will fail with EBUSY.
3733 can be in danger of a stack overflow, and corruption will occur,
3738 at every function call that will become very useful. As ftrace provides