mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
synced 2026-04-23 21:27:36 -04:00
9fa48a2477
Parsing and formating timerlat data might consume a reasonable amount of CPU time on very large systems, or when timerlat has a too short period. Add an option to run timerlat with auto-analysis enabled while skipping the statistics parsing. In this mode, rtla timerlat periodically checks if the tracing is on, going to sleep waiting for the stop tracing condition to stop tracing, or for the tracing session to finish. If the stop tracing condition is hit, the tool prints the auto analysis. Otherwise, the tool prints the max observed latency and exit. The max observed latency is captured via tracing_max_latency. Link: https://lore.kernel.org/linux-trace-devel/4dc514d1d5dc353c537a466a9b5af44c266b6da2.1680106912.git.bristot@kernel.org Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
15 lines
516 B
ReStructuredText
15 lines
516 B
ReStructuredText
**--dump-tasks**
|
|
|
|
prints the task running on all CPUs if stop conditions are met (depends on !--no-aa)
|
|
|
|
**--no-aa**
|
|
|
|
disable auto-analysis, reducing rtla timerlat cpu usage
|
|
|
|
**--aa-only** *us*
|
|
|
|
Set stop tracing conditions and run without collecting and displaying statistics.
|
|
Print the auto-analysis if the system hits the stop tracing condition. This option
|
|
is useful to reduce rtla timerlat CPU, enabling the debug without the overhead of
|
|
collecting the statistics.
|