Commit fc64e4ad authored by Srivatsa S. Bhat (VMware)'s avatar Srivatsa S. Bhat (VMware) Committed by Steven Rostedt (VMware)

tracing/hwlat: Don't ignore outer-loop duration when calculating max_latency

max_latency is intended to record the maximum ever observed hardware
latency, which may occur in either part of the loop (inner/outer). So
we need to also consider the outer-loop sample when updating
max_latency.

Link: http://lkml.kernel.org/r/157073345463.17189.18124025522664682811.stgit@srivatsa-ubuntu

Fixes: e7c15cd8 ("tracing: Added hardware latency tracer")
Cc: stable@vger.kernel.org
Signed-off-by: default avatarSrivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
Signed-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
parent 98dc19c1
...@@ -256,6 +256,8 @@ static int get_sample(void) ...@@ -256,6 +256,8 @@ static int get_sample(void)
/* Keep a running maximum ever recorded hardware latency */ /* Keep a running maximum ever recorded hardware latency */
if (sample > tr->max_latency) if (sample > tr->max_latency)
tr->max_latency = sample; tr->max_latency = sample;
if (outer_sample > tr->max_latency)
tr->max_latency = outer_sample;
} }
out: out:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment