Differences

This shows you the differences between two versions of the page.

--- realtime:documentation:howto:tools:rtla [2024/09/30 15:17]
costa.shul events
+++ realtime:documentation:howto:tools:rtla [2025/12/11 12:39] (current)
tglozar [Calling into external tooling] Add link to rtla with perf processor trace tutorial
@@ Line 1: / Line 1: @@
 ====== Real-time Linux Analysis tool ======
-The **rtla** – Real-time Linux Analysis tool set analyzes real-time properties of the Linux kernel.
+The **rtla** – Real-time Linux Analysis toolset analyzes real-time properties of the Linux kernel.
 The tools has several modes. The default **top** mode displays periodic summary from a tracer. The **hist** mode displays histogram at the end of operation. Automatic mode <nowiki>(--auto)</nowiki> stops when the threshold is reached.
@@ Line 13: / Line 13: @@
   * [[https://docs.kernel.org/tools/rtla/rtla-osnoise.html|rtla osnoise]] provides information about operating system noise measured with [[https://docs.kernel.org/trace/osnoise-tracer.html|osnoise tracer]]. It dispatches kernel threads per CPU to measure various sources of interference during execution, such as preemption, softirq, and IRQs. Modes: [[https://docs.kernel.org/tools/rtla/rtla-osnoise-top.html|top]], [[https://docs.kernel.org/tools/rtla/rtla-osnoise-hist.html|hist]].
-  * [[https://docs.kernel.org/tools/rtla/rtla-hwnoise.html|rtla hwnoise]] detects and quantifies hardware-related noise with [[https://docs.kernel.org/trace/osnoise-tracer.html|osnoise tracer]]. By disabling interrupts and scheduling of threads, only non-maskable interrupts and hardware-related noise are analyzed.
+  * [[https://docs.kernel.org/tools/rtla/rtla-hwnoise.html|rtla hwnoise]] detects and quantifies hardware-related noise with [[https://docs.kernel.org/trace/osnoise-tracer.html|osnoise tracer]]. By disabling interrupts with [[https://elixir.bootlin.com/linux/v6.12.6/A/ident/OSN_IRQ_DISABLE|OSNOISE_IRQ_DISABLE]] and scheduling of threads, only non-maskable interrupts and hardware-related noise are analyzed.
 Each of these commands has various options for configuration, such as setting tracer periods, runtimes, thresholds, scheduling parameters, trace events and triggers, and more. These commands offer different ways to analyze and understand the real-time properties and noise sources in the Linux operating system.
+===== System tuning ======
+**rtla** commands include several command line options that can be used to tune various parameters of the system affecting its real-time properties.
+  * //--dma-latency <n>// - this holds /dev/cpu_dma_latency at the specified value during the measurement. Note that unlike cyclictest, the option is not enabled by default in rtla.
+  * //--deepest-idle-state <n>// - limits the deepest allowed idle state via cpuidle interface, only on CPUs where measurement is running, unlike --dma-latency, which affects all CPUs.
+Setting the deepest idle state instead of DMA latency helps with power consumption, but might lead to increased latencies on some systems.
 ===== Events =====
-Arguments to enable common events for automatic and trace options:
+All **rtla** tools include //latency source auto-analysis//, enabled with //-a <us>// option, which takes the duration of a latency in microseconds for rtla to stop tracing at. Auto-analysis uses tracepoints to capture thread and IRQ interference to the real-time workload, which are collected, processed, and finally formatted and printed at the end of the measurement.
+If auto-analysis is not enough to determine the cause of the latency, additional tracepoints may be enabled using the //-e <event_name>// option. Arguments to enable common events for automatic and trace options:
 ''<nowiki>
@@ Line 30: / Line 40: @@
 grep 1 /sys/kernel/debug/tracing/instances/ /sys/kernel/debug/tracing/events/ -R --include enable
 </nowiki>''
+To be able to see captured events after the end of the rtla run, trace output has to be enabled using the //--trace/-t// option, unless -a is used, which enables //-t// automatically.
+===== Calling into external tooling =====
+Since version 6.17, **rtla** supports integrating external tools into latency measurement by the means of //actions//. Actions can run a command or send a signal to a process whenever tracing is stopped on latency threshold set with //-T/-i/-a// (for timerlat; //-s/-S/-a// for osnoise), or at the end of tracing. A special action resumes tracing after stop, if requested.
+External tooling might be used in cases where rtla's tracefs-based diagnostics are insufficient. See the rtla manpages for how to use actions. One specific use of actions is covered in the tutorial, [[realtime:documentation:howto:tools:rtla:processor_trace|Using rtla with perf processor trace]].
 ===== More Information =====
-  * [[https://bristot.me/linux-scheduling-latency-debug-and-analysis/|Linux scheduling latency debug and analysis with RTLA]]
+[[realtime:documentation:howto:tools:start|RT tools and utilities]]\\
-  * [[https://www.youtube.com/watch?v=oLTRVcJ7_as|🎥 rtla timerlat: Debugging Real-time Linux Scheduling Latency, video]]
+[[https://bristot.me/linux-scheduling-latency-debug-and-analysis/|Linux scheduling latency debug and analysis with RTLA]]\\
-  * [[https://elixir.bootlin.com/linux/latest/source/tools/tracing/rtla|user mode source]]
+[[https://www.youtube.com/watch?v=oLTRVcJ7_as|🎥 rtla timerlat: Debugging Real-time Linux Scheduling Latency, video]]\\
-  * [[https://elixir.bootlin.com/linux/latest/source/kernel/trace/trace_osnoise.c|trace_osnoise.c - kernel mode source]]
+[[https://elixir.bootlin.com/linux/latest/source/tools/tracing/rtla|user mode source]]\\
+[[https://elixir.bootlin.com/linux/latest/source/kernel/trace/trace_osnoise.c#L1531|trace_osnoise.c: trace_sample_threshold() - kernel mode source]]\\
+RTLA uses [[https://man7.org/linux/man-pages/man3/libtracefs.3.html|libtracefs]]

Wiki

User Tools

Site Tools

Differences

Page Tools