Lines Matching full:trace
27 See Documentation/trace/ftrace-design.rst
32 See Documentation/trace/ftrace-design.rst
45 See Documentation/trace/ftrace-design.rst
95 See Documentation/trace/ftrace-design.rst
245 Enable the kernel to trace every kernel function. This is done
261 Enable the kernel to trace a function at both its return
263 Its first purpose is to trace the duration of functions and
277 enable it via the trace option funcgraph-retval.
278 See Documentation/trace/ftrace.rst
288 enable it via the trace option funcgraph-retaddr.
298 enabled via the trace option func-args (for the function tracer) and
311 can function trace, and this table is linked into the kernel
350 bool "Function trace tracing code"
355 for debugging to trace some of the tracing infratructure itself.
392 bool "Trace max stack"
403 stack-trace saved. If this is configured with DYNAMIC_FTRACE
501 The output will appear in the trace and trace_pipe files.
542 The output will appear in the trace and trace_pipe files.
570 events can be used to trace the source of interference from NMI,
585 See Documentation/trace/mmiotrace.rst.
589 bool "Trace process context switches and events"
593 This tracer hooks to various trace points in the kernel,
594 allowing the user to pick and choose which trace point they
595 want to trace. It also includes the sched_switch tracer plugin.
598 bool "Trace syscalls"
611 Some system call trace events will record the data from a user
620 bool "Create a snapshot trace buffer"
646 trace recording, as it needs to add some checks to synchronize
681 bool "Trace likely/unlikely profiler"
712 Selected by tracers that will trace the likely and unlikely
718 bool "Trace likely/unlikely instances"
724 "Trace likely/unlikely profiler" is that this is not a
726 events into a running trace buffer to see when and where the
741 Say Y here if you want to be able to trace the block layer actions
750 echo 1 > /sys/block/sda/sda1/trace/enable
793 Documentation/trace/kprobetrace.rst for more details.
833 dynamic events (similar to tracepoints) on the fly via the trace
913 bool "Synthetic trace events"
918 Synthetic events are user-defined trace events that can be
919 used to combine data from other trace events or in fact any
921 via the trace() action of histogram triggers or directly
924 See Documentation/trace/events.rst or
925 Documentation/trace/histogram.rst for details and examples.
930 bool "User trace events"
934 User trace events are user-defined trace events that
935 can be used like an existing kernel trace event. User trace
941 See Documentation/trace/user_events.rst.
953 Hist triggers allow one or more arbitrary trace event fields
963 See Documentation/trace/histogram.rst.
967 bool "Trace event injection"
970 Allow user-space to inject a specific trace event into the ring
1022 bool "Show eval mappings for trace events"
1025 The "print fmt" of the trace events will show the enum/sizeof names
1039 names matched with their values and what trace event system they
1127 bool "Run selftest on trace events"
1131 This option performs a test on all trace events in the system.
1242 To test, insert the module, and then check the trace buffer
1254 To test, insert the module, and then check the trace buffer
1273 Documentation/trace/histogram-design.rst.
1282 source "kernel/trace/rv/Kconfig"