realtime:documentation:howto:tools:rtla
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
realtime:documentation:howto:tools:rtla [2025/12/04 15:42] tglozar [Events] Typo + formatting |
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 27: | Line 27: | ||
| ===== Events ===== | ===== Events ===== | ||
| - | 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. | + | 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 <name> option. Arguments to enable common events for automatic and trace options: | + | 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> | ''<nowiki> | ||
| Line 41: | Line 41: | ||
| </nowiki>'' | </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. | + | 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 ===== | ===== More Information ===== | ||
realtime/documentation/howto/tools/rtla.1764862934.txt.gz · Last modified: 2025/12/04 15:42 by tglozar
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
