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
40 See Documentation/trace/ftrace-design.rst
64 but does not want them included in the ftrace locations.
69 See Documentation/trace/ftrace-design.rst
74 See Documentation/trace/ftrace-design.rst
79 Arch supports the gcc options -pg with -mfentry
84 Arch supports the gcc options -pg with -mrecord-mcount and -nop-mcount
89 Arch supports objtool --mcount
94 Arch supports the objtool options --mcount with --mnop.
96 of ftrace locations.
182 menuconfig FTRACE config
189 if FTRACE
192 bool "Boot-time Tracing support"
196 Enable developer to setup ftrace subsystem via supplemental
211 by using a compiler feature to insert a small, 5-byte No-Operation
216 small and not measurable even in micro-benchmarks (at least on
242 enable it via the trace option funcgraph-retval.
243 See Documentation/trace/ftrace.rst
253 replace them with a No-Op instruction) on boot up. During
254 compile time, a table is made of all the locations that ftrace
295 This option enables kernel function probe (fprobe) based on ftrace.
328 stack-trace saved. If this is configured with DYNAMIC_FTRACE
347 bool "Interrupts-off Latency Tracer"
357 This option measures the time spent in irqs-off critical
361 disabled by default and can be runtime (re-)started
366 (Note that kernel size and overhead increase with this option
367 enabled. This option and the preempt-off timing option can be
371 bool "Preemption-off Latency Tracer"
381 This option measures the time spent in preemption-off critical
385 disabled by default and can be runtime (re-)started
390 (Note that kernel size and overhead increase with this option
391 enabled. This option and the irqs-off timing option can be
420 hwlat_detector/width - time in usecs for how long to spin for
421 hwlat_detector/window - time in usecs between the start of each
426 for "window - width" microseconds, where the system can
445 In the context of high-performance computing (HPC), the Operating
449 can cause noise to the system. Moreover, hardware-related jobs can
456 increasing a per-cpu interference counter. It saves an interference
461 hardware noise counter increases, pointing to a hardware-related
481 to find sources of wakeup latencies of real-time threads.
483 The tracer creates a per-cpu kernel thread with real-time priority.
511 default and can be enabled at run-time.
538 ftrace interface, e.g.:
578 The "all branch" profiler will profile every if-statement in the
660 Tracing also is possible using the ftrace interface, e.g.:
671 bool "Enable fprobe-based dynamic events"
678 exit via ftrace interface. The syntax is same as the kprobe events
697 bool "Enable kprobes-based dynamic events"
704 on the fly via the ftrace interface. See
710 This option is also required by perf-probe subcommand of perf tools.
719 This is only for the developers who want to debug ftrace itself
722 If kprobes can use ftrace instead of breakpoint, ftrace related
723 functions are protected from kprobe-events to prevent an infinite
728 events on ftrace functions for debugging ftrace by itself.
734 bool "Enable uprobes-based dynamic events"
748 This option is required if you plan to use perf-probe subcommand
786 depends on $(cc-option,-mrecord-mcount)
809 tracing_map is a special-purpose lock-free map for tracing,
810 separated out as a stand-alone facility in order to allow it
821 Synthetic events are user-defined trace events that can be
825 by way of an in-kernel API.
837 User trace events are user-defined trace events that
863 Inter-event tracing of quantities such as latencies is also
873 Allow user-space to inject a specific trace event into the ring
914 any other users of the ring buffer (such as ftrace). It then creates
975 size at runtime.
986 place where recursion was detected into the ftrace "recursed_functions"
992 bool "Enable GCOV profiling on ftrace subsystem"
995 Enable GCOV profiling on ftrace subsystem for checking
1000 Note that on a kernel compiled with this config, ftrace will
1007 bool "Perform a startup test on ftrace"
1011 This option performs a series of startup tests on ftrace. On bootup
1014 tracers of ftrace.
1035 TBD - enable a way to actually call the syscalls as we test their
1039 bool "Verify compile time sorting of ftrace functions"
1044 where the ftrace knows where to patch functions for tracing
1046 is not done correctly, it will cause non-deterministic failures.
1058 a thread per cpu. Each thread will write various size events
1115 irq-disabled critical sections for 500us:
1125 tristate "Test module for in-kernel synthetic event generation"
1129 functionality of in-kernel synthetic event definition and
1138 tristate "Test module for in-kernel kprobe event generation"
1142 functionality of in-kernel kprobe event definition.
1159 - Helps developers verify that nothing is broken.
1161 - Provides educational information to support the details
1163 Documentation/trace/histogram-design.rst.
1174 endif # FTRACE