This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
realtime:documentation:howto:tools:rtla [2025/12/05 09:44] tglozar [Calling into external tooling] Clarify version |
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 47: | Line 47: | ||
| 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. | 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. | + | 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 ===== | ||