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
37 See Documentation/trace/ftrace-design.rst
58 but does not want them included in the ftrace locations.
63 See Documentation/trace/ftrace-design.rst
68 See Documentation/trace/ftrace-design.rst
73 Arch supports the gcc options -pg with -mfentry
78 Arch supports the gcc options -pg with -mrecord-mcount and -nop-mcount
83 Arch supports objtool --mcount
169 menuconfig FTRACE config
176 if FTRACE
179 bool "Boot-time Tracing support"
183 Enable developer to setup ftrace subsystem via supplemental
198 by using a compiler feature to insert a small, 5-byte No-Operation
203 small and not measurable even in micro-benchmarks (at least on
228 replace them with a No-Op instruction) on boot up. During
229 compile time, a table is made of all the locations that ftrace
266 This option enables kernel function probe (fprobe) based on ftrace.
299 stack-trace saved. If this is configured with DYNAMIC_FTRACE
318 bool "Interrupts-off Latency Tracer"
328 This option measures the time spent in irqs-off critical
332 disabled by default and can be runtime (re-)started
337 (Note that kernel size and overhead increase with this option
338 enabled. This option and the preempt-off timing option can be
342 bool "Preemption-off Latency Tracer"
352 This option measures the time spent in preemption-off critical
356 disabled by default and can be runtime (re-)started
361 (Note that kernel size and overhead increase with this option
362 enabled. This option and the irqs-off timing option can be
390 hwlat_detector/width - time in usecs for how long to spin for
391 hwlat_detector/window - time in usecs between the start of each
396 for "window - width" microseconds, where the system can
414 In the context of high-performance computing (HPC), the Operating
418 can cause noise to the system. Moreover, hardware-related jobs can
425 increasing a per-cpu interference counter. It saves an interference
430 hardware noise counter increases, pointing to a hardware-related
450 to find sources of wakeup latencies of real-time threads.
452 The tracer creates a per-cpu kernel thread with real-time priority.
480 default and can be enabled at run-time.
507 ftrace interface, e.g.:
547 The "all branch" profiler will profile every if-statement in the
629 Tracing also is possible using the ftrace interface, e.g.:
640 bool "Enable kprobes-based dynamic events"
647 on the fly via the ftrace interface. See
653 This option is also required by perf-probe subcommand of perf tools.
662 This is only for the developers who want to debug ftrace itself
665 If kprobes can use ftrace instead of breakpoint, ftrace related
666 functions are protected from kprobe-events to prevent an infinite
671 events on ftrace functions for debugging ftrace by itself.
677 bool "Enable uprobes-based dynamic events"
691 This option is required if you plan to use perf-probe subcommand
729 depends on $(cc-option,-mrecord-mcount)
752 tracing_map is a special-purpose lock-free map for tracing,
753 separated out as a stand-alone facility in order to allow it
764 Synthetic events are user-defined trace events that can be
768 by way of an in-kernel API.
781 User trace events are user-defined trace events that
786 an associated byte being non-zero.
806 Inter-event tracing of quantities such as latencies is also
816 Allow user-space to inject a specific trace event into the ring
857 any other users of the ring buffer (such as ftrace). It then creates
918 size at runtime.
929 place where recursion was detected into the ftrace "recursed_functions"
935 bool "Enable GCOV profiling on ftrace subsystem"
938 Enable GCOV profiling on ftrace subsystem for checking
943 Note that on a kernel compiled with this config, ftrace will
950 bool "Perform a startup test on ftrace"
954 This option performs a series of startup tests on ftrace. On bootup
957 tracers of ftrace.
978 TBD - enable a way to actually call the syscalls as we test their
982 bool "Verify compile time sorting of ftrace functions"
987 where the ftrace knows where to patch functions for tracing
989 is not done correctly, it will cause non-deterministic failures.
1001 a thread per cpu. Each thread will write various size events
1058 irq-disabled critical sections for 500us:
1068 tristate "Test module for in-kernel synthetic event generation"
1072 functionality of in-kernel synthetic event definition and
1081 tristate "Test module for in-kernel kprobe event generation"
1085 functionality of in-kernel kprobe event definition.
1102 - Helps developers verify that nothing is broken.
1104 - Provides educational information to support the details
1106 Documentation/trace/histogram-design.rst.
1117 endif # FTRACE