From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Daniel Bristot de Oliveira <bristot@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-trace-devel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] rtla: Timerlat auto-analysis
Date: Tue, 31 Jan 2023 16:38:52 +0100 [thread overview]
Message-ID: <cover.1675179318.git.bristot@kernel.org> (raw)
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
next reply other threads:[~2023-01-31 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 15:38 Daniel Bristot de Oliveira [this message]
2023-01-31 15:38 ` [PATCH 1/3] rtla/timerlat: Add auto-analysis core Daniel Bristot de Oliveira
2023-01-31 15:38 ` [PATCH 2/3] rtla/timerlat: Add auto-analysis support to timerlat top Daniel Bristot de Oliveira
2023-01-31 15:38 ` [PATCH 3/3] Documentation/rtla: Add timerlat-top auto-analysis options Daniel Bristot de Oliveira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1675179318.git.bristot@kernel.org \
--to=bristot@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).