[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADDUTFx+tfdkLp=wp-XH-U1iB3ZM90W=ktbR4ckp62pDmUGPMg@mail.gmail.com>
Date: Sat, 22 Jul 2023 11:04:29 +0300
From: Costa Shulyupin <costa.shul@...hat.com>
To: Daniel Bristot de Oliveira <bristot@...nel.org>
Cc: linux-rt-users@...r.kernel.org,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Jonathan Corbet <corbet@....net>,
"open list:TRACING" <linux-kernel@...r.kernel.org>,
"open list:TRACING" <linux-trace-kernel@...r.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH] tracing/timerlat: Add latency threshold
> rtla timerlat has the --aa-only that ignores the trace until
> the tracing stops, and then do the auto-analysis based on the
> tail of the trace.
> So, as I said, I am not convinced that adding this interface file is
> better than setting the stop-tracing option... and then waiting for
> the trace to stop... parsing only the tail of the buffer.
I see. Stop-tracing option of rtla timerlat solves the problem for
most of the cases.
Thank you very much!
Costa
Powered by blists - more mailing lists