Lines Matching +full:allow +full:- +full:set +full:- +full:time
1 # SPDX-License-Identifier: GPL-2.0-only
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
65 If this is set, then arguments and stack can be found from
74 If this is set, ftrace_regs has pt_regs, thus it can convert to
86 See Documentation/trace/ftrace-design.rst
91 Arch supports the gcc options -pg with -mfentry
96 Arch supports the gcc options -pg with -mrecord-mcount and -nop-mcount
101 Arch supports objtool --mcount
106 Arch supports the objtool options --mcount with --mnop.
119 at build time.
126 Sort the mcount_loc section at build time.
150 Allow the use of ring_buffer_swap_cpu.
217 bool "Boot-time Tracing support"
222 kernel cmdline at boot time for debugging (tracing) driver
236 by using a compiler feature to insert a small, 5-byte No-Operation
241 small and not measurable even in micro-benchmarks (at least on
267 enable it via the trace option funcgraph-retval.
278 enable it via the trace option funcgraph-retaddr.
288 enabled via the trace option func-args (for the function tracer) and
289 funcgraph-args (for the function graph tracer)
299 replace them with a No-Op instruction) on boot up. During
300 compile time, a table is made of all the locations that ftrace
373 stack-trace saved. If this is configured with DYNAMIC_FTRACE
392 bool "Interrupts-off Latency Tracer"
402 This option measures the time spent in irqs-off critical
406 disabled by default and can be runtime (re-)started
412 enabled. This option and the preempt-off timing option can be
416 bool "Preemption-off Latency Tracer"
426 This option measures the time spent in preemption-off critical
430 disabled by default and can be runtime (re-)started
436 enabled. This option and the irqs-off timing option can be
455 depending on what the cpumask file is set to, which each thread
459 time, this tracer will detect it. This is useful for testing
460 if a system is reliable for Real Time tasks.
465 hwlat_detector/width - time in usecs for how long to spin for
466 hwlat_detector/window - time in usecs between the start of each
471 for "window - width" microseconds, where the system can
482 file. Every time a latency is greater than tracing_thresh, it will
490 In the context of high-performance computing (HPC), the Operating
494 can cause noise to the system. Moreover, hardware-related jobs can
501 increasing a per-cpu interference counter. It saves an interference
506 hardware noise counter increases, pointing to a hardware-related
512 In addition to the tracer, a set of tracepoints were added to
526 to find sources of wakeup latencies of real-time threads.
528 The tracer creates a per-cpu kernel thread with real-time priority.
532 the current time and the absolute time that the timer was set
556 default and can be enabled at run-time.
582 Allow tracing users to take snapshot of the current buffer using the
589 bool "Allow snapshot to swap per CPU"
593 Allow doing a snapshot of a single CPU buffer instead of a
594 full swap (all buffers). If this is set, then the following is
623 The "all branch" profiler will profile every if-statement in the
716 bool "Enable fprobe-based dynamic events"
742 bool "Enable kprobes-based dynamic events"
755 This option is also required by perf-probe subcommand of perf tools.
768 functions are protected from kprobe-events to prevent an infinite
779 bool "Enable uprobes-based dynamic events"
793 This option is required if you plan to use perf-probe subcommand
797 bool "Enable event-based dynamic events"
832 set a different return value. This is used for error injection.
840 depends on $(cc-option,-mrecord-mcount)
863 tracing_map is a special-purpose lock-free map for tracing,
864 separated out as a stand-alone facility in order to allow it
875 Synthetic events are user-defined trace events that can be
879 by way of an in-kernel API.
891 User trace events are user-defined trace events that
910 Hist triggers allow one or more arbitrary trace event fields
917 Inter-event tracing of quantities such as latencies is also
927 Allow user-space to inject a specific trace event into the ring
938 run), and calls the tracepoint. Each iteration will record the time
941 will report the time it took to do the previous tracepoint.
943 to keep the time the same. The initial string is simply a write of
944 "START". The second string records the cold cache time of the first
1091 This may take some time run as there are a lot of events.
1099 with the event enabled. This adds a bit more time for kernel boot
1102 TBD - enable a way to actually call the syscalls as we test their
1106 bool "Verify compile time sorting of ftrace functions"
1112 and other callbacks is done at compile time. But if the sort
1113 is not done correctly, it will cause non-deterministic failures.
1114 When this is set, the sorted sections will be verified that they
1132 The test runs for 10 seconds. This will slow your boot time
1143 bool "Verify ring buffer time stamp deltas"
1146 This will audit the time stamps on the ring buffer sub
1147 buffer to make sure that all the time deltas for the
1148 events on a sub buffer matches the current time stamp.
1153 add up to be greater than the current time stamp.
1182 irq-disabled critical sections for 500us:
1192 tristate "Test module for in-kernel synthetic event generation"
1196 functionality of in-kernel synthetic event definition and
1205 tristate "Test module for in-kernel kprobe event generation"
1209 functionality of in-kernel kprobe event definition.
1226 - Helps developers verify that nothing is broken.
1228 - Provides educational information to support the details
1230 Documentation/trace/histogram-design.rst.