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
59 If this is set, then arguments and stack can be found from
68 If this is set, ftrace_regs has pt_regs, thus it can convert to
80 See Documentation/trace/ftrace-design.rst
85 See Documentation/trace/ftrace-design.rst
90 Arch supports the gcc options -pg with -mfentry
95 Arch supports the gcc options -pg with -mrecord-mcount and -nop-mcount
100 Arch supports objtool --mcount
105 Arch supports the objtool options --mcount with --mnop.
118 at build time.
125 Sort the mcount_loc section at build time.
149 Allow the use of ring_buffer_swap_cpu.
203 bool "Boot-time Tracing support"
208 kernel cmdline at boot time for debugging (tracing) driver
222 by using a compiler feature to insert a small, 5-byte No-Operation
227 small and not measurable even in micro-benchmarks (at least on
253 enable it via the trace option funcgraph-retval.
264 enable it via the trace option funcgraph-retaddr.
274 replace them with a No-Op instruction) on boot up. During
275 compile time, a table is made of all the locations that ftrace
348 stack-trace saved. If this is configured with DYNAMIC_FTRACE
367 bool "Interrupts-off Latency Tracer"
377 This option measures the time spent in irqs-off critical
381 disabled by default and can be runtime (re-)started
387 enabled. This option and the preempt-off timing option can be
391 bool "Preemption-off Latency Tracer"
401 This option measures the time spent in preemption-off critical
405 disabled by default and can be runtime (re-)started
411 enabled. This option and the irqs-off timing option can be
430 depending on what the cpumask file is set to, which each thread
434 time, this tracer will detect it. This is useful for testing
435 if a system is reliable for Real Time tasks.
440 hwlat_detector/width - time in usecs for how long to spin for
441 hwlat_detector/window - time in usecs between the start of each
446 for "window - width" microseconds, where the system can
457 file. Every time a latency is greater than tracing_thresh, it will
465 In the context of high-performance computing (HPC), the Operating
469 can cause noise to the system. Moreover, hardware-related jobs can
476 increasing a per-cpu interference counter. It saves an interference
481 hardware noise counter increases, pointing to a hardware-related
487 In addition to the tracer, a set of tracepoints were added to
501 to find sources of wakeup latencies of real-time threads.
503 The tracer creates a per-cpu kernel thread with real-time priority.
507 the current time and the absolute time that the timer was set
531 default and can be enabled at run-time.
557 Allow tracing users to take snapshot of the current buffer using the
564 bool "Allow snapshot to swap per CPU"
568 Allow doing a snapshot of a single CPU buffer instead of a
569 full swap (all buffers). If this is set, then the following is
598 The "all branch" profiler will profile every if-statement in the
691 bool "Enable fprobe-based dynamic events"
717 bool "Enable kprobes-based dynamic events"
730 This option is also required by perf-probe subcommand of perf tools.
743 functions are protected from kprobe-events to prevent an infinite
754 bool "Enable uprobes-based dynamic events"
768 This option is required if you plan to use perf-probe subcommand
793 set a different return value. This is used for error injection.
806 depends on $(cc-option,-mrecord-mcount)
829 tracing_map is a special-purpose lock-free map for tracing,
830 separated out as a stand-alone facility in order to allow it
841 Synthetic events are user-defined trace events that can be
845 by way of an in-kernel API.
857 User trace events are user-defined trace events that
876 Hist triggers allow one or more arbitrary trace event fields
883 Inter-event tracing of quantities such as latencies is also
893 Allow user-space to inject a specific trace event into the ring
904 run), and calls the tracepoint. Each iteration will record the time
907 will report the time it took to do the previous tracepoint.
909 to keep the time the same. The initial string is simply a write of
910 "START". The second string records the cold cache time of the first
1057 This may take some time run as there are a lot of events.
1065 with the event enabled. This adds a bit more time for kernel boot
1068 TBD - enable a way to actually call the syscalls as we test their
1072 bool "Verify compile time sorting of ftrace functions"
1078 and other callbacks is done at compile time. But if the sort
1079 is not done correctly, it will cause non-deterministic failures.
1080 When this is set, the sorted sections will be verified that they
1098 The test runs for 10 seconds. This will slow your boot time
1109 bool "Verify ring buffer time stamp deltas"
1112 This will audit the time stamps on the ring buffer sub
1113 buffer to make sure that all the time deltas for the
1114 events on a sub buffer matches the current time stamp.
1119 add up to be greater than the current time stamp.
1148 irq-disabled critical sections for 500us:
1158 tristate "Test module for in-kernel synthetic event generation"
1162 functionality of in-kernel synthetic event definition and
1171 tristate "Test module for in-kernel kprobe event generation"
1175 functionality of in-kernel kprobe event definition.
1192 - Helps developers verify that nothing is broken.
1194 - Provides educational information to support the details
1196 Documentation/trace/histogram-design.rst.