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 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
326 This option enables kernel function probe (fprobe) based on 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
397 (Note that kernel size and overhead increase with this option
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
421 (Note that kernel size and overhead increase with this option
422 enabled. This option and the irqs-off timing option can be
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
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
512 to find sources of wakeup latencies of real-time threads.
514 The tracer creates a per-cpu kernel thread with real-time priority.
542 default and can be enabled at run-time.
569 ftrace interface, e.g.:
609 The "all branch" profiler will profile every if-statement in the
691 Tracing also is possible using the ftrace interface, e.g.:
702 bool "Enable fprobe-based dynamic events"
709 exit via ftrace interface. The syntax is same as the kprobe events
728 bool "Enable kprobes-based dynamic events"
735 on the fly via the ftrace interface. See
741 This option is also required by perf-probe subcommand of perf tools.
750 This is only for the developers who want to debug ftrace itself
753 If kprobes can use ftrace instead of breakpoint, ftrace related
754 functions are protected from kprobe-events to prevent an infinite
759 events on ftrace functions for debugging ftrace by itself.
765 bool "Enable uprobes-based dynamic events"
779 This option is required if you plan to use perf-probe subcommand
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
894 Inter-event tracing of quantities such as latencies is also
904 Allow user-space to inject a specific trace event into the ring
945 any other users of the ring buffer (such as ftrace). It then creates
1006 size at runtime.
1009 bool "Validate RCU is on during ftrace execution"
1015 ftrace (and other users of ftrace_test_recursion_trylock()) are not
1030 place where recursion was detected into the ftrace "recursed_functions"
1036 bool "Enable GCOV profiling on ftrace subsystem"
1039 Enable GCOV profiling on ftrace subsystem for checking
1044 Note that on a kernel compiled with this config, ftrace will
1051 bool "Perform a startup test on ftrace"
1055 This option performs a series of startup tests on ftrace. On bootup
1058 tracers of ftrace.
1079 TBD - enable a way to actually call the syscalls as we test their
1083 bool "Verify compile time sorting of ftrace functions"
1088 where the ftrace knows where to patch functions for tracing
1090 is not done correctly, it will cause non-deterministic failures.
1102 a thread per cpu. Each thread will write various size events
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.
1218 endif # FTRACE