diff options
author | 2019-10-10 11:51:01 -0700 | |
---|---|---|
committer | 2019-10-12 20:49:33 -0400 | |
commit | fc64e4ad80d4b72efce116f87b3174f0b7196f8e (patch) | |
tree | f4c1f3db8217dd7afa8b988c19684535b1d04068 /scripts/gdb/linux/utils.py | |
parent | tracing/hwlat: Report total time spent in all NMIs during the sample (diff) | |
download | wireguard-linux-fc64e4ad80d4b72efce116f87b3174f0b7196f8e.tar.xz wireguard-linux-fc64e4ad80d4b72efce116f87b3174f0b7196f8e.zip |
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: e7c15cd8a113 ("tracing: Added hardware latency tracer")
Cc: stable@vger.kernel.org
Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions