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
40 See Documentation/trace/ftrace-design.rst
57 This allows for use of ftrace_regs_get_argument() and
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.
150 # All tracer options should select GENERIC_TRACER. For those options that are
173 # Minimum requirements an architecture has to meet for us to
192 bool "Boot-time Tracing support"
197 kernel cmdline at boot time for debugging (tracing) driver
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
229 draw a call graph for each thread with some information like
242 enable it via the trace option funcgraph-retval.
253 replace them with a No-Op instruction) on boot up. During
296 The fprobe is similar to kprobes, but probes only for kernel function
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
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
391 enabled. This option and the irqs-off timing option can be
405 bool "Tracer to detect hardware latencies (like SMIs)"
411 spinning in a loop looking for interruptions caused by
412 something other than the kernel. For example, if a
414 time, this tracer will detect it. This is useful for testing
415 if a system is reliable for Real Time tasks.
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
425 for "width" microseconds in every "window" cycle. It will not spin
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
450 also cause noise, for example, via SMIs.
456 increasing a per-cpu interference counter. It saves an interference
457 counter for each source of interference. The interference counter for
461 hardware noise counter increases, pointing to a hardware-related
462 noise. In this way, osnoise can account for any source of
465 available for the thread, and the counters for the noise sources.
481 to find sources of wakeup latencies of real-time threads.
483 The tracer creates a per-cpu kernel thread with real-time priority.
485 to sleep waiting for the timer to fire. At the wakeup, the thread
508 Mmiotrace traces Memory Mapped I/O access and is meant for
511 default and can be enabled at run-time.
554 After which, only the tracing buffer for CPU 2 was swapped with
578 The "all branch" profiler will profile every if-statement in the
644 bool "Support for tracing block IO actions"
655 on a block device queue. For more information (and the userspace
671 bool "Enable fprobe-based dynamic events"
686 bool "Support BTF function arguments for probe events"
697 bool "Enable kprobes-based dynamic events"
705 Documentation/trace/kprobetrace.rst for more details.
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
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
773 set a different return value. This is used for error injection.
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.
828 Documentation/trace/histogram.rst for details and examples.
837 User trace events are user-defined trace events that
858 reading a debugfs/tracefs file. They're useful for
860 event activity as an initial guide for further investigation
863 Inter-event tracing of quantities such as latencies is also
873 Allow user-space to inject a specific trace event into the ring
874 buffer. This is mainly used for testing purpose.
915 a producer and consumer that will run for 10 seconds and sleep for
925 bool "Show eval mappings for trace events"
929 instead of their values. This can cause problems for user space tools
940 This option is for debugging the conversions. A file is created
947 they are needed for the "eval_map" file. Enabling this option will
995 Enable GCOV profiling on ftrace subsystem for checking
1032 with the event enabled. This adds a bit more time for kernel boot
1035 TBD - enable a way to actually call the syscalls as we test their
1044 where the ftrace knows where to patch functions for tracing
1046 is not done correctly, it will cause non-deterministic failures.
1065 The test runs for 10 seconds. This will slow your boot time
1080 buffer to make sure that all the time deltas for the
1082 This audit is performed for every event that is not
1096 tristate "Test module for mmiotrace"
1099 This is a dumb module for testing mmiotrace. It is very dangerous
1111 configurable delay. The module busy waits for the duration of the
1114 For example, the following invocation generates a burst of three
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
1133 for the generated sample events.
1138 tristate "Test module for in-kernel kprobe event generation"
1142 functionality of in-kernel kprobe event definition.
1145 for the generated kprobe events.
1153 Add "hist_debug" file for each event, which when read will
1159 - Helps developers verify that nothing is broken.
1161 - Provides educational information to support the details
1163 Documentation/trace/histogram-design.rst.