Lines Matching +full:ftrace +full:- +full:size
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
75 but does not want them included in the ftrace locations.
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.
107 of ftrace locations.
193 menuconfig FTRACE config
200 if FTRACE
203 bool "Boot-time Tracing support"
207 Enable developer to setup ftrace subsystem via supplemental
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.
254 See Documentation/trace/ftrace.rst
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
315 This option enables kernel function probe (fprobe) based on 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
386 (Note that kernel size and overhead increase with this option
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
410 (Note that kernel size and overhead increase with this option
411 enabled. This option and the irqs-off timing option can be
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
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
501 to find sources of wakeup latencies of real-time threads.
503 The tracer creates a per-cpu kernel thread with real-time priority.
531 default and can be enabled at run-time.
558 ftrace interface, e.g.:
598 The "all branch" profiler will profile every if-statement in the
680 Tracing also is possible using the ftrace interface, e.g.:
691 bool "Enable fprobe-based dynamic events"
698 exit via ftrace interface. The syntax is same as the kprobe events
717 bool "Enable kprobes-based dynamic events"
724 on the fly via the ftrace interface. See
730 This option is also required by perf-probe subcommand of perf tools.
739 This is only for the developers who want to debug ftrace itself
742 If kprobes can use ftrace instead of breakpoint, ftrace related
743 functions are protected from kprobe-events to prevent an infinite
748 events on ftrace functions for debugging ftrace by itself.
754 bool "Enable uprobes-based dynamic events"
768 This option is required if you plan to use perf-probe subcommand
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
883 Inter-event tracing of quantities such as latencies is also
893 Allow user-space to inject a specific trace event into the ring
934 any other users of the ring buffer (such as ftrace). It then creates
995 size at runtime.
998 bool "Validate RCU is on during ftrace execution"
1004 ftrace (and other users of ftrace_test_recursion_trylock()) are not
1019 place where recursion was detected into the ftrace "recursed_functions"
1025 bool "Enable GCOV profiling on ftrace subsystem"
1028 Enable GCOV profiling on ftrace subsystem for checking
1033 Note that on a kernel compiled with this config, ftrace will
1040 bool "Perform a startup test on ftrace"
1044 This option performs a series of startup tests on ftrace. On bootup
1047 tracers of ftrace.
1068 TBD - enable a way to actually call the syscalls as we test their
1072 bool "Verify compile time sorting of ftrace functions"
1077 where the ftrace knows where to patch functions for tracing
1079 is not done correctly, it will cause non-deterministic failures.
1091 a thread per cpu. Each thread will write various size events
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.
1207 endif # FTRACE