tracing/timerlat: Notify new max thread latency
authorDaniel Bristot de Oliveira <bristot@kernel.org>
Wed, 29 Mar 2023 15:50:15 +0000 (17:50 +0200)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Mon, 3 Apr 2023 15:52:32 +0000 (11:52 -0400)
timerlat is not reporting a new tracing_max_latency for the thread
latency. The reason is that it is not calling notify_new_max_latency()
function after the new thread latency is sampled.

Call notify_new_max_latency() after computing the thread latency.

Link: https://lkml.kernel.org/r/16e18d61d69073d0192ace07bf61e405cca96e9c.1680104184.git.bristot@kernel.org
Cc: stable@vger.kernel.org
Fixes: dae181349f1e ("tracing/osnoise: Support a list of trace_array *tr")
Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
kernel/trace/trace_osnoise.c

index 9176bb7a9bb459399b7518e3a1caf24e01d7a16f..e8116094bed86bf8486232ce77efdf5a491878e5 100644 (file)
@@ -1738,6 +1738,8 @@ static int timerlat_main(void *data)
 
                trace_timerlat_sample(&s);
 
+               notify_new_max_latency(diff);
+
                timerlat_dump_stack(time_to_us(diff));
 
                tlat->tracing_thread = false;