From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: linux-trace-devel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>,
William White <chwhite@redhat.com>,
Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: [PATCH 0/8] rtla improvements
Date: Thu, 11 May 2023 20:04:18 +0200 [thread overview]
Message-ID: <cover.1683827510.git.bristot@kernel.org> (raw)
This is a series of improvements for rtla, mainly as a result of our
daily usage of the tool debugging problems at red hat.
The cgroup support and house keeping options are from our usage
of the tool debugging containers.
The auto-analysis overhead reduction is needed when we go to
large boxes - but it is really hand in practice, as it gives an idea
of the problem without having to look at the trace.
Finally, running hwnoise 100 % of CPU time might cause some systems
to slow down too much. Reduce its utilization to 75% by default to
avoid problems for people using it for the first time.
Daniel Bristot de Oliveira (8):
rtla: Add -C cgroup support
rtla: Add --house-keeping option
rtla: Change monitored_cpus from char * to cpu_set_t
rtla: Automatically move rtla to a house-keeping cpu
rtla/timerlat: Give timerlat auto analysis its own instance
rtla/timerlat_hist: Add auto-analysis support
rtla: Start the tracers after creating all instances
rtla/hwnoise: Reduce runtime to 75%
Documentation/tools/rtla/common_options.rst | 8 +
.../tools/rtla/common_timerlat_aa.rst | 7 -
.../tools/rtla/rtla-timerlat-hist.rst | 7 +-
.../tools/rtla/rtla-timerlat-top.rst | 7 +
tools/tracing/rtla/src/osnoise_hist.c | 90 +++++-
tools/tracing/rtla/src/osnoise_top.c | 83 +++++-
tools/tracing/rtla/src/timerlat_aa.c | 35 ++-
tools/tracing/rtla/src/timerlat_aa.h | 5 +-
tools/tracing/rtla/src/timerlat_hist.c | 139 +++++++--
tools/tracing/rtla/src/timerlat_top.c | 127 +++++++--
tools/tracing/rtla/src/utils.c | 266 ++++++++++++++++--
tools/tracing/rtla/src/utils.h | 5 +
12 files changed, 684 insertions(+), 95 deletions(-)
--
2.38.1
next reply other threads:[~2023-05-11 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 18:04 Daniel Bristot de Oliveira [this message]
2023-05-11 18:04 ` [PATCH 1/8] rtla: Add -C cgroup support Daniel Bristot de Oliveira
2023-05-11 18:04 ` [PATCH 2/8] rtla: Add --house-keeping option Daniel Bristot de Oliveira
2023-05-11 18:04 ` [PATCH 3/8] rtla: Change monitored_cpus from char * to cpu_set_t Daniel Bristot de Oliveira
2023-05-11 18:04 ` [PATCH 4/8] rtla: Automatically move rtla to a house-keeping cpu Daniel Bristot de Oliveira
2023-05-11 18:04 ` [PATCH 5/8] rtla/timerlat: Give timerlat auto-analysis its own instance Daniel Bristot de Oliveira
2023-05-11 18:04 ` [PATCH 6/8] rtla/timerlat_hist: Add auto-analysis support Daniel Bristot de Oliveira
2023-05-11 18:04 ` [PATCH 7/8] rtla: Start the tracers after creating all instances Daniel Bristot de Oliveira
2023-05-11 18:04 ` [PATCH 8/8] rtla/hwnoise: Reduce runtime to 75% Daniel Bristot de Oliveira
2023-05-11 18:04 ` 0001-rtla-Add-C-cgroup-support.patch Daniel Bristot de Oliveira
2023-05-11 18:08 ` 0001-rtla-Add-C-cgroup-support.patch 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.1683827510.git.bristot@kernel.org \
--to=bristot@kernel.org \
--cc=chwhite@redhat.com \
--cc=juri.lelli@redhat.com \
--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).