lkml.org 
[lkml]   [2023]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH 0/3] rtla: Timerlat auto-analysis
Date
Currently, timerlat displays the timerlat tracer latency results, saving
the intuitive timerlat trace for the developer to analyze.

This patch goes a step forward in the automaton of the scheduling latency
analysis by providing a summary of the root cause of a latency higher than
the passed "stop tracing" parameter if the trace stops.

The output is intuitive enough for non-expert users to have a general idea
of the root cause by looking at each factor's contribution percentage
while keeping the technical detail in the output for more expert users
to start an in dept debug or to correlate a root cause with an existing one.

The first patch adds the functionality without using it. The second attaches
it to the timerlat top, and the last one updates the man page.

Daniel Bristot de Oliveira (3):
rtla/timerlat: Add auto-analysis core
rtla/timerlat: Add auto-analysis support to timerlat top
Documentation/rtla: Add timerlat-top auto-analysis options

.../tools/rtla/common_timerlat_aa.rst | 7 +
.../tools/rtla/rtla-timerlat-top.rst | 164 ++-
tools/tracing/rtla/src/timerlat_aa.c | 990 ++++++++++++++++++
tools/tracing/rtla/src/timerlat_aa.h | 12 +
tools/tracing/rtla/src/timerlat_top.c | 46 +-
tools/tracing/rtla/src/utils.h | 3 +
6 files changed, 1129 insertions(+), 93 deletions(-)
create mode 100644 Documentation/tools/rtla/common_timerlat_aa.rst
create mode 100644 tools/tracing/rtla/src/timerlat_aa.c
create mode 100644 tools/tracing/rtla/src/timerlat_aa.h

--
2.38.1

\
 
 \ /
  Last update: 2023-03-27 00:03    [W:0.025 / U:0.956 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site