From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
John Kacur <jkacur@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: [GIT PULL] tracing/tools: Updates for 6.10
Date: Fri, 17 May 2024 10:41:26 +0200 [thread overview]
Message-ID: <20240517084128.173825-1-bristot@kernel.org> (raw)
Steven,
RTLA:
Specific for timerlat:
- Improves the output of timerlat top by adding a missing \n,
and by avoiding printing color-formatting characters where
they are translated to regular characters.
- Improves timerlat auto-analysis output by replacing '\t'
with spaces to avoid copy-and-paste issues when reporting
problems.
- For timerlat, make the user-space (-u) option the default,
as it is the most complete test. Add a -k option to use
the in-kernel workload.
- On timerlat top and hist, add a summary with the overall
results. For instance, the minimum value for all CPUs,
the overall average and the maximum value from all CPUs.
- timerlat hist was printing initial values (i.e., 0 as max,
and ~0 as min) if the trace stopped before the first Ret-User
event. This problem was fixed by printing the " - "
no value string to the output if that was the case.
For all RTLA tools:
- Add a --warm-up <seconds> option, allowing the workload to
run for <seconds> before starting to collect results.
- Add a --trace-buffer-size option, allowing the user to set
the tracing buffer size for -t option. This option is mainly
useful for reducing the trace file. Now rtla depends on
libtracefs >= 1.6.
- Fix the -t [trace_file] parsing, now it does not require
the '=' before the option parameter, and better handles the
multiple ways a user can pass the trace_file.txt
Please pull the latest trace-tools-v6.10 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/bristot/linux.git
trace-tools-v6.10
Tag SHA1: dbd633e7f81bac0114f609ff2eade9f4e66a28e2
Head SHA1: 59c22f70b2951d81de410d477ae536ba951b4f37
Daniel Bristot de Oliveira (8):
rtla/timerlat: Simplify "no value" printing on top
rtla/auto-analysis: Replace \t with spaces
rtla/timerlat: Use pretty formatting only on interactive tty
rtla/timerlat: Add a summary for top mode
rtla/timerlat: Add a summary for hist mode
rtla: Add the --warm-up option
rtla/timerlat: Make user-space threads the default
rtla: Add --trace-buffer-size option
John Kacur (3):
rtla/timerlat: Fix histogram report when a cpu count is 0
rtla: Fix -t\--trace[=file]
rtla: Documentation: Fix -t, --trace
----
Documentation/tools/rtla/common_options.rst | 11 +-
.../tools/rtla/common_osnoise_options.rst | 4 +
.../tools/rtla/common_timerlat_options.rst | 10 +-
tools/tracing/rtla/Makefile.config | 2 +-
tools/tracing/rtla/src/osnoise_hist.c | 55 +++-
tools/tracing/rtla/src/osnoise_top.c | 55 +++-
tools/tracing/rtla/src/timerlat_aa.c | 109 ++++----
tools/tracing/rtla/src/timerlat_hist.c | 294 ++++++++++++++++++---
tools/tracing/rtla/src/timerlat_top.c | 250 +++++++++++++++---
tools/tracing/rtla/src/trace.c | 15 ++
tools/tracing/rtla/src/trace.h | 1 +
11 files changed, 653 insertions(+), 153 deletions(-)
reply other threads:[~2024-05-17 8:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240517084128.173825-1-bristot@kernel.org \
--to=bristot@kernel.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@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 read-only IMAP folder(s) and NNTP newsgroup(s).