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:50] tglozar [Events] More 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 42: | Line 42: | ||
| 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 ===== | ||