Lines Matching +full:buffer +full:- +full:enable
1 # SPDX-License-Identifier: GPL-2.0-only
20 Enable generic return hooking feature. This is an internal
21 API, which will be used by other function-entry hooking
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
100 Arch supports the gcc options -pg with -mfentry
105 Arch supports the gcc options -pg with -mrecord-mcount and -nop-mcount
110 Arch supports objtool --mcount
115 Arch supports the objtool options --mcount with --mnop.
116 An architecture can select this if it wants to enable nop'ing
209 Enable the kernel tracing infrastructure.
227 bool "Boot-time Tracing support"
231 Enable developer to setup ftrace subsystem via supplemental
245 Enable the kernel to trace every kernel function. This is done
246 by using a compiler feature to insert a small, 5-byte No-Operation
251 small and not measurable even in micro-benchmarks (at least on
261 Enable the kernel to trace a function at both its return
277 enable it via the trace option funcgraph-retval.
288 enable it via the trace option funcgraph-retaddr.
298 enabled via the trace option func-args (for the function tracer) and
299 funcgraph-args (for the function graph tracer)
309 replace them with a No-Op instruction) on boot up. During
356 Enable this to allow some of the tracing infrastructure to be traced
403 stack-trace saved. If this is configured with DYNAMIC_FTRACE
407 To enable the stack tracer on bootup, pass in 'stacktrace'
422 bool "Interrupts-off Latency Tracer"
431 This option measures the time spent in irqs-off critical
435 disabled by default and can be runtime (re-)started
441 enabled. This option and the preempt-off timing option can be
445 bool "Preemption-off Latency Tracer"
454 This option measures the time spent in preemption-off critical
458 disabled by default and can be runtime (re-)started
464 enabled. This option and the irqs-off timing option can be
492 hwlat_detector/width - time in usecs for how long to spin for
493 hwlat_detector/window - time in usecs between the start of each
498 for "window - width" microseconds, where the system can
508 To enable this tracer, echo in "hwlat" into the current_tracer
510 be recorded into the ring buffer.
517 In the context of high-performance computing (HPC), the Operating
521 can cause noise to the system. Moreover, hardware-related jobs can
528 increasing a per-cpu interference counter. It saves an interference
533 hardware noise counter increases, pointing to a hardware-related
544 To enable this tracer, echo in "osnoise" into the current_tracer
553 to find sources of wakeup latencies of real-time threads.
555 The tracer creates a per-cpu kernel thread with real-time priority.
583 default and can be enabled at run-time.
620 bool "Create a snapshot trace buffer"
622 Allow tracing users to take snapshot of the current buffer using the
636 Allow doing a snapshot of a single CPU buffer instead of a
642 After which, only the tracing buffer for CPU 2 was swapped with
643 the main tracing buffer, and the other CPU buffers remain the same.
666 The "all branch" profiler will profile every if-statement in the
667 kernel. This profiler will also enable the likely/unlikely
677 Only enable it if you want to analyse the branching behavior.
726 events into a running trace buffer to see when and where the
750 echo 1 > /sys/block/sda/sda1/trace/enable
759 bool "Enable fprobe-based dynamic events"
783 bool "Dump of dynamic probe event fetch-arguments"
787 This shows the dump of fetch-arguments of dynamic probe events
791 it might be a security risk. Only enable it if you need to debug
797 bool "Enable kprobes-based dynamic events"
810 This option is also required by perf-probe subcommand of perf tools.
823 functions are protected from kprobe-events to prevent an infinite
834 bool "Enable uprobes-based dynamic events"
848 This option is required if you plan to use perf-probe subcommand
852 bool "Enable event-based dynamic events"
881 bool "Enable BPF programs to override a kprobed function"
895 depends on $(cc-option,-mrecord-mcount)
918 tracing_map is a special-purpose lock-free map for tracing,
919 separated out as a stand-alone facility in order to allow it
930 Synthetic events are user-defined trace events that can be
934 by way of an in-kernel API.
946 User trace events are user-defined trace events that
972 Inter-event tracing of quantities such as latencies is also
982 Allow user-space to inject a specific trace event into the ring
983 buffer. This is mainly used for testing purpose.
1018 tristate "Ring buffer benchmark stress tester"
1021 This option creates a test to stress the ring buffer and benchmark it.
1022 It creates its own ring buffer such that it will not interfere with
1023 any other users of the ring buffer (such as ftrace). It then creates
1100 bool "Record functions that recurse in the ring buffer"
1105 The ring buffer has its own internal recursion. Although when
1114 bool "Enable GCOV profiling on ftrace subsystem"
1117 Enable GCOV profiling on ftrace subsystem for checking
1152 This option will also enable testing every syscall event.
1157 TBD - enable a way to actually call the syscalls as we test their
1168 is not done correctly, it will cause non-deterministic failures.
1175 bool "Ring buffer startup self test"
1178 Run a simple self test on the ring buffer on boot up. Late in the
1181 into the ring buffer. Another thread is created to send IPIs
1183 to the ring buffer, to test/stress the nesting ability.
1191 It will output the stats of each per cpu buffer: What
1198 bool "Verify ring buffer time stamp deltas"
1201 This will audit the time stamps on the ring buffer sub
1202 buffer to make sure that all the time deltas for the
1203 events on a sub buffer matches the current time stamp.
1207 that all the deltas on the previous sub buffer do not
1211 and should only be used to test the logic of the ring buffer.
1218 bool "Enable persistent ring buffer error injection test"
1222 buffer is named "ptracingtest". and if so, it will corrupt some
1224 persistent ring buffer can recover from some of its sub-buffers
1227 ring buffer, e.g.
1234 echo 1 > events/enable
1237 echo c > /proc/sysrq-trigger
1242 Note that events for the test ring buffer needs to be enabled
1243 prior to crashing the kernel so that the ring buffer has content
1246 ring buffer, it should not be used for any other purpose other
1271 irq-disabled critical sections for 500us:
1281 tristate "Test module for in-kernel synthetic event generation"
1285 functionality of in-kernel synthetic event definition and
1288 To test, insert the module, and then check the trace buffer
1294 tristate "Test module for in-kernel kprobe event generation"
1298 functionality of in-kernel kprobe event definition.
1300 To test, insert the module, and then check the trace buffer
1315 - Helps developers verify that nothing is broken.
1317 - Provides educational information to support the details
1319 Documentation/trace/histogram-design.rst.
1341 This trace remote includes a ring-buffer writer implementation using