From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: [GIT PULL] tracing/rtla: Updates to the RTLA tool
Date: Mon, 21 Mar 2022 10:30:35 -0400 [thread overview]
Message-ID: <20220321103035.564a1df5@gandalf.local.home> (raw)
Linus,
I'm sending this as a separate pull request from my normal tracing tree, as
it had dependencies to commits in your tree but not in my development
branch. As it only affects the tools/ directory, I kept it separate as it
has no changes to the kernel itself.
Real Time Linux Analysis Tool updates for 5.18
Changes to RTLA:
- Support for adjusting tracing_threashold
- Add -a (auto) option to make it easier for users to debug in the field
- Add -e option to add more events to the trace
- Add --trigger option to add triggers to events
- Add --filter option to filter events
- Add support to save histograms to the file
- Add --dma-latency to set /dev/cpu_dma_latency
- Other fixes and cleanups
Please pull the latest trace-rtla-v5.18 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-rtla-v5.18
Tag SHA1: cc921ea64d6df1bb8955ff5762dbcdc408e34264
Head SHA1: 75016ca3acd0de79868ef5b0694195fe05288ade
Daniel Bristot de Oliveira (15):
rtla/osnoise: Add support to adjust the tracing_thresh
rtla/osnoise: Add an option to set the threshold
rtla/osnoise: Add the automatic trace option
rtla/timerlat: Add the automatic trace option
rtla/trace: Add trace events helpers
rtla: Add -e/--event support
rtla/trace: Add trace event trigger helpers
rtla: Add --trigger support
rtla/trace: Add trace event filter helpers
rtla: Add --filter support
rtla/trace: Save event histogram output to a file
rtla: Check for trace off also in the trace instance
rtla/osnoise: Fix osnoise hist stop tracing message
rtla/timerlat: Add --dma-latency option
rtla: Tools main loop cleanup
----
Documentation/tools/rtla/common_options.rst | 19 ++
.../tools/rtla/common_osnoise_options.rst | 10 +
.../tools/rtla/common_timerlat_options.rst | 12 +
tools/tracing/rtla/src/osnoise.c | 83 +++++
tools/tracing/rtla/src/osnoise.h | 8 +
tools/tracing/rtla/src/osnoise_hist.c | 95 +++++-
tools/tracing/rtla/src/osnoise_top.c | 91 +++++-
tools/tracing/rtla/src/timerlat_hist.c | 108 ++++++-
tools/tracing/rtla/src/timerlat_top.c | 103 +++++-
tools/tracing/rtla/src/trace.c | 345 +++++++++++++++++++++
tools/tracing/rtla/src/trace.h | 23 ++
tools/tracing/rtla/src/utils.c | 33 ++
tools/tracing/rtla/src/utils.h | 1 +
13 files changed, 903 insertions(+), 28 deletions(-)
---------------------------
next reply other threads:[~2022-03-21 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:30 Steven Rostedt [this message]
2022-03-23 18:15 ` Linus Torvalds
2022-03-23 19:32 ` Daniel Bristot de Oliveira
2022-03-23 19:43 ` Steven Rostedt
2022-03-23 19:52 ` Daniel Bristot de Oliveira
2022-03-23 19:26 ` 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=20220321103035.564a1df5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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®