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 enabled via the trace option func-args (for the function tracer) and
275 funcgraph-args (for the function graph tracer)
285 replace them with a No-Op instruction) on boot up. During
286 compile time, a table is made of all the locations that ftrace
359 stack-trace saved. If this is configured with DYNAMIC_FTRACE
378 bool "Interrupts-off Latency Tracer"
388 This option measures the time spent in irqs-off critical
392 disabled by default and can be runtime (re-)started
398 enabled. This option and the preempt-off timing option can be
402 bool "Preemption-off Latency Tracer"
412 This option measures the time spent in preemption-off critical
416 disabled by default and can be runtime (re-)started
422 enabled. This option and the irqs-off timing option can be
441 depending on what the cpumask file is set to, which each thread
445 time, this tracer will detect it. This is useful for testing
446 if a system is reliable for Real Time tasks.
451 hwlat_detector/width - time in usecs for how long to spin for
452 hwlat_detector/window - time in usecs between the start of each
457 for "window - width" microseconds, where the system can
468 file. Every time a latency is greater than tracing_thresh, it will
476 In the context of high-performance computing (HPC), the Operating
480 can cause noise to the system. Moreover, hardware-related jobs can
487 increasing a per-cpu interference counter. It saves an interference
492 hardware noise counter increases, pointing to a hardware-related
498 In addition to the tracer, a set of tracepoints were added to
512 to find sources of wakeup latencies of real-time threads.
514 The tracer creates a per-cpu kernel thread with real-time priority.
518 the current time and the absolute time that the timer was set
542 default and can be enabled at run-time.
568 Allow tracing users to take snapshot of the current buffer using the
575 bool "Allow snapshot to swap per CPU"
579 Allow doing a snapshot of a single CPU buffer instead of a
580 full swap (all buffers). If this is set, then the following is
609 The "all branch" profiler will profile every if-statement in the
702 bool "Enable fprobe-based dynamic events"
728 bool "Enable kprobes-based dynamic events"
741 This option is also required by perf-probe subcommand of perf tools.
754 functions are protected from kprobe-events to prevent an infinite
765 bool "Enable uprobes-based dynamic events"
779 This option is required if you plan to use perf-probe subcommand
804 set a different return value. This is used for error injection.
817 depends on $(cc-option,-mrecord-mcount)
840 tracing_map is a special-purpose lock-free map for tracing,
841 separated out as a stand-alone facility in order to allow it
852 Synthetic events are user-defined trace events that can be
856 by way of an in-kernel API.
868 User trace events are user-defined trace events that
887 Hist triggers allow one or more arbitrary trace event fields
894 Inter-event tracing of quantities such as latencies is also
904 Allow user-space to inject a specific trace event into the ring
915 run), and calls the tracepoint. Each iteration will record the time
918 will report the time it took to do the previous tracepoint.
920 to keep the time the same. The initial string is simply a write of
921 "START". The second string records the cold cache time of the first
1068 This may take some time run as there are a lot of events.
1076 with the event enabled. This adds a bit more time for kernel boot
1079 TBD - enable a way to actually call the syscalls as we test their
1083 bool "Verify compile time sorting of ftrace functions"
1089 and other callbacks is done at compile time. But if the sort
1090 is not done correctly, it will cause non-deterministic failures.
1091 When this is set, the sorted sections will be verified that they
1109 The test runs for 10 seconds. This will slow your boot time
1120 bool "Verify ring buffer time stamp deltas"
1123 This will audit the time stamps on the ring buffer sub
1124 buffer to make sure that all the time deltas for the
1125 events on a sub buffer matches the current time stamp.
1130 add up to be greater than the current time stamp.
1159 irq-disabled critical sections for 500us:
1169 tristate "Test module for in-kernel synthetic event generation"
1173 functionality of in-kernel synthetic event definition and
1182 tristate "Test module for in-kernel kprobe event generation"
1186 functionality of in-kernel kprobe event definition.
1203 - Helps developers verify that nothing is broken.
1205 - Provides educational information to support the details
1207 Documentation/trace/histogram-design.rst.