Lines Matching +full:required +full:- +full:for +full:- +full:hardware +full:- +full:jobs
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
62 This allows for use of ftrace_regs_get_argument() and
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.
161 # All tracer options should select GENERIC_TRACER. For those options that are
184 # Minimum requirements an architecture has to meet for us to
203 bool "Boot-time Tracing support"
208 kernel cmdline at boot time for debugging (tracing) driver
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
240 draw a call graph for each thread with some information like
253 enable it via the trace option funcgraph-retval.
264 enable it via the trace option funcgraph-retaddr.
274 replace them with a No-Op instruction) on boot up. During
316 The fprobe is similar to kprobes, but probes only for kernel function
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
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
411 enabled. This option and the irqs-off timing option can be
425 bool "Tracer to detect hardware latencies (like SMIs)"
431 spinning in a loop looking for interruptions caused by
432 something other than the kernel. For example, if a
434 time, this tracer will detect it. This is useful for testing
435 if a system is reliable for Real Time tasks.
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
445 for "width" microseconds in every "window" cycle. It will not spin
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
470 also cause noise, for example, via SMIs.
476 increasing a per-cpu interference counter. It saves an interference
477 counter for each source of interference. The interference counter for
481 hardware noise counter increases, pointing to a hardware-related
482 noise. In this way, osnoise can account for any source of
485 available for the thread, and the counters for the noise sources.
501 to find sources of wakeup latencies of real-time threads.
503 The tracer creates a per-cpu kernel thread with real-time priority.
505 to sleep waiting for the timer to fire. At the wakeup, the thread
528 Mmiotrace traces Memory Mapped I/O access and is meant for
531 default and can be enabled at run-time.
574 After which, only the tracing buffer for CPU 2 was swapped with
598 The "all branch" profiler will profile every if-statement in the
664 bool "Support for tracing block IO actions"
675 on a block device queue. For more information (and the userspace
691 bool "Enable fprobe-based dynamic events"
706 bool "Support BTF function arguments for probe events"
717 bool "Enable kprobes-based dynamic events"
725 Documentation/trace/kprobetrace.rst for more details.
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
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
793 set a different return value. This is used for error injection.
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.
848 Documentation/trace/histogram.rst for details and examples.
857 User trace events are user-defined trace events that
878 reading a debugfs/tracefs file. They're useful for
880 event activity as an initial guide for further investigation
883 Inter-event tracing of quantities such as latencies is also
893 Allow user-space to inject a specific trace event into the ring
894 buffer. This is mainly used for testing purpose.
935 a producer and consumer that will run for 10 seconds and sleep for
945 bool "Show eval mappings for trace events"
949 instead of their values. This can cause problems for user space tools
960 This option is for debugging the conversions. A file is created
967 they are needed for the "eval_map" file. Enabling this option will
1028 Enable GCOV profiling on ftrace subsystem for checking
1065 with the event enabled. This adds a bit more time for kernel boot
1068 TBD - enable a way to actually call the syscalls as we test their
1077 where the ftrace knows where to patch functions for tracing
1079 is not done correctly, it will cause non-deterministic failures.
1098 The test runs for 10 seconds. This will slow your boot time
1113 buffer to make sure that all the time deltas for the
1115 This audit is performed for every event that is not
1129 tristate "Test module for mmiotrace"
1132 This is a dumb module for testing mmiotrace. It is very dangerous
1144 configurable delay. The module busy waits for the duration of the
1147 For example, the following invocation generates a burst of three
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
1166 for the generated sample events.
1171 tristate "Test module for in-kernel kprobe event generation"
1175 functionality of in-kernel kprobe event definition.
1178 for the generated kprobe events.
1186 Add "hist_debug" file for each event, which when read will
1192 - Helps developers verify that nothing is broken.
1194 - Provides educational information to support the details
1196 Documentation/trace/histogram-design.rst.