From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: [for-next][PATCH 00/11] tracing/tools: Updates for 6.5
Date: Tue, 13 Jun 2023 18:07:50 -0400 [thread overview]
Message-ID: <20230613220750.330146797@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
tools/for-next
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-06-13 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 22:07 Steven Rostedt [this message]
2023-06-13 22:07 ` [for-next][PATCH 01/11] rtla: Add -C cgroup support Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 02/11] rtla: Add --house-keeping option Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 03/11] rtla: Change monitored_cpus from char * to cpu_set_t Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 04/11] rtla: Automatically move rtla to a house-keeping cpu Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 05/11] rtla/timerlat: Give timerlat auto analysis its own instance Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 06/11] rtla/timerlat_hist: Add auto-analysis support Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 07/11] rtla: Start the tracers after creating all instances Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 08/11] rtla/hwnoise: Reduce runtime to 75% Steven Rostedt
2023-06-13 22:07 ` [for-next][PATCH 09/11] rtla/timerlat_top: Add timerlat user-space support Steven Rostedt
2023-06-13 22:08 ` [for-next][PATCH 10/11] rtla/timerlat_hist: " Steven Rostedt
2023-06-13 22:08 ` [for-next][PATCH 11/11] Documentation: Add tools/rtla timerlat -u option documentation Steven Rostedt
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=20230613220750.330146797@goodmis.org \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.