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
81 but does not want them included in the ftrace locations.
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.
108 of ftrace locations.
194 menuconfig FTRACE config
201 if FTRACE
217 bool "Boot-time Tracing support"
221 Enable developer to setup ftrace subsystem via supplemental
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.
268 See Documentation/trace/ftrace.rst
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
340 This option enables kernel function probe (fprobe) based on 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
411 (Note that kernel size and overhead increase with this option
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
435 (Note that kernel size and overhead increase with this option
436 enabled. This option and the irqs-off timing option can be
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
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
526 to find sources of wakeup latencies of real-time threads.
528 The tracer creates a per-cpu kernel thread with real-time priority.
556 default and can be enabled at run-time.
583 ftrace interface, e.g.:
623 The "all branch" profiler will profile every if-statement in the
705 Tracing also is possible using the ftrace interface, e.g.:
716 bool "Enable fprobe-based dynamic events"
723 exit via ftrace interface. The syntax is same as the kprobe events
742 bool "Enable kprobes-based dynamic events"
749 on the fly via the ftrace interface. See
755 This option is also required by perf-probe subcommand of perf tools.
764 This is only for the developers who want to debug ftrace itself
767 If kprobes can use ftrace instead of breakpoint, ftrace related
768 functions are protected from kprobe-events to prevent an infinite
773 events on ftrace functions for debugging ftrace by itself.
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"
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
917 Inter-event tracing of quantities such as latencies is also
927 Allow user-space to inject a specific trace event into the ring
968 any other users of the ring buffer (such as ftrace). It then creates
1029 size at runtime.
1032 bool "Validate RCU is on during ftrace execution"
1038 ftrace (and other users of ftrace_test_recursion_trylock()) are not
1053 place where recursion was detected into the ftrace "recursed_functions"
1059 bool "Enable GCOV profiling on ftrace subsystem"
1062 Enable GCOV profiling on ftrace subsystem for checking
1067 Note that on a kernel compiled with this config, ftrace will
1074 bool "Perform a startup test on ftrace"
1078 This option performs a series of startup tests on ftrace. On bootup
1081 tracers of ftrace.
1102 TBD - enable a way to actually call the syscalls as we test their
1106 bool "Verify compile time sorting of ftrace functions"
1111 where the ftrace knows where to patch functions for tracing
1113 is not done correctly, it will cause non-deterministic failures.
1125 a thread per cpu. Each thread will write various size events
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.
1241 endif # FTRACE