Lines Matching full:tracing
139 Adds a very slight overhead to tracing when enabled.
144 select TRACING
151 # enabled by all tracers (context switch and event tracer) they select TRACING.
154 # GENERIC_TRACER and TRACING to avoid circular dependencies to accomplish the
157 config TRACING config
170 select TRACING
174 # be able to offer generic tracing facilities:
187 Enable the kernel tracing infrastructure.
192 bool "Boot-time Tracing support"
193 depends on TRACING
197 kernel cmdline at boot time for debugging (tracing) driver
214 tracing is enabled by the administrator. If it's runtime disabled
246 bool "enable/disable function tracing dynamically"
251 This option will modify all the calls to function tracing
260 See the files in /sys/kernel/tracing:
266 otherwise has native performance as long as no tracing is active.
324 kernel and displays it in /sys/kernel/tracing/stack_trace.
364 echo 0 > /sys/kernel/tracing/tracing_max_latency
388 echo 0 > /sys/kernel/tracing/tracing_max_latency
417 Some files are created in the tracing directory when this
504 bool "Memory mapped IO tracing"
510 implementation and works via page faults. Tracing is disabled by
519 select TRACING
537 Allow tracing users to take snapshot of the current buffer using the
540 echo 1 > /sys/kernel/tracing/snapshot
552 echo 1 > /sys/kernel/tracing/per_cpu/cpu2/snapshot
554 After which, only the tracing buffer for CPU 2 was swapped with
555 the main tracing buffer, and the other CPU buffers remain the same.
599 /sys/kernel/tracing/trace_stat/branch_annotated
612 /sys/kernel/tracing/trace_stat/branch_all
626 profiled. Profiling the tracing infrastructure can only happen
644 bool "Support for tracing block IO actions"
654 on a given queue. Tracing allows you to see any traffic happening
660 Tracing also is possible using the ftrace interface, e.g.:
663 echo blk > /sys/kernel/tracing/current_tracer
664 cat /sys/kernel/tracing/trace_pipe
672 select TRACING
677 This allows user to add tracing events on the function entry and
698 select TRACING
703 This allows the user to add tracing events (similar to tracepoints)
741 select TRACING
744 This allows the user to add tracing events on top of userspace
809 tracing_map is a special-purpose lock-free map for tracing,
817 select TRACING
834 select TRACING
840 processes can determine if their tracing events should be
851 select TRACING
863 Inter-event tracing of quantities such as latencies is also
871 depends on TRACING
926 depends on TRACING
941 in the tracing directory called "eval_map" that will show the
953 bool "Record functions that recurse in function tracing"
956 All callbacks that attach to the function tracing have some sort
1044 where the ftrace knows where to patch functions for tracing