From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: [GIT PULL] tracing tooling: Updates for 6.5
Date: Tue, 4 Jul 2023 09:29:42 -0400 [thread overview]
Message-ID: <20230704092942.6d140594@rorschach.local.home> (raw)
Linus,
[ As the merge window opened up while I was in Prague, I almost forgot
about the tooling branch (even though I was also with Daniel who did
all these changes!) ]
Tracing tooling updates for 6.5:
- Add cgroup support for rtla via the -C option
- Add --house-keeping option that tells rtla where to place the housekeeping
threads.
- Have rtla/timerlat have its own tracing instance instead of using the top
level tracing instance that is the default for other tracing users to use.
- Add auto analysis to timerlat_hist
- Have rtla start the tracers after creating the instances
- Reduce rtla hwnoise down to 75% from 100% as it runs with preemption disabled
and can cause system instability at 100%.
- Add support to run timerlat_top and timerlat_hist threads in user-space
instead of just using the kernel tasks.
- Some minor clean ups and documentation changes.
Please pull the latest trace-tools-v6.5 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace-tools-v6.5
Tag SHA1: 9dedca3671c6bfa589bd14415a71e69d40d83b3d
Head SHA1: 6127383217741615f3450b684ecbee1ff570ee98
Daniel Bristot de Oliveira (11):
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%
rtla/timerlat_top: Add timerlat user-space support
rtla/timerlat_hist: Add timerlat user-space support
Documentation: Add tools/rtla timerlat -u option documentation
----
Documentation/tools/rtla/common_options.rst | 8 +
Documentation/tools/rtla/common_timerlat_aa.rst | 7 -
.../tools/rtla/common_timerlat_options.rst | 7 +
Documentation/tools/rtla/rtla-timerlat-hist.rst | 7 +-
Documentation/tools/rtla/rtla-timerlat-top.rst | 7 +
tools/tracing/rtla/src/osnoise.c | 65 +++++
tools/tracing/rtla/src/osnoise.h | 5 +
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 | 262 +++++++++++++++--
tools/tracing/rtla/src/timerlat_top.c | 229 +++++++++++++--
tools/tracing/rtla/src/timerlat_u.c | 224 ++++++++++++++
tools/tracing/rtla/src/timerlat_u.h | 18 ++
tools/tracing/rtla/src/utils.c | 324 +++++++++++++++++++--
tools/tracing/rtla/src/utils.h | 7 +
17 files changed, 1277 insertions(+), 106 deletions(-)
create mode 100644 tools/tracing/rtla/src/timerlat_u.c
create mode 100644 tools/tracing/rtla/src/timerlat_u.h
---------------------------
next reply other threads:[~2023-07-04 13:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 13:29 Steven Rostedt [this message]
2023-07-05 18:19 ` pr-tracker-bot
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=20230704092942.6d140594@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®