From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Tomas Glozar <tglozar@redhat.com>, John Kacur <jkacur@redhat.com>
Subject: [for-next][PATCH 00/10] tools/tracing: Updates for v6.15
Date: Thu, 06 Mar 2025 13:18:01 -0500 [thread overview]
Message-ID: <20250306181801.485766945@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
tools/for-next
Head SHA1: dc4d4e7c72d17e6f6bdd9ce0d7a72a085828987f
Costa Shulyupin (1):
rtla: Refactor save_trace_to_file
Tomas Glozar (9):
rtla/timerlat: Unify params struct
tools/build: Add bpftool-skeletons feature test
rtla: Add optional dependency on BPF tooling
rtla/timerlat: Add BPF skeleton to collect samples
rtla/timerlat_hist: Use BPF to collect samples
rtla/timerlat_top: Move divisor to update
rtla/timerlat_top: Use BPF to collect samples
rtla/timerlat: Test BPF mode
tools/rv: Keep user LDFLAGS in build
----
tools/build/Makefile.feature | 3 +-
tools/build/feature/Makefile | 3 +
tools/scripts/Makefile.include | 3 +
tools/tracing/rtla/.gitignore | 1 +
tools/tracing/rtla/Makefile | 20 +-
tools/tracing/rtla/Makefile.config | 42 ++++
tools/tracing/rtla/src/Build | 1 +
tools/tracing/rtla/src/osnoise.h | 2 +
tools/tracing/rtla/src/osnoise_hist.c | 5 +-
tools/tracing/rtla/src/osnoise_top.c | 5 +-
tools/tracing/rtla/src/timerlat.bpf.c | 149 +++++++++++++
tools/tracing/rtla/src/timerlat.h | 54 +++++
tools/tracing/rtla/src/timerlat_aa.c | 2 -
tools/tracing/rtla/src/timerlat_bpf.c | 166 +++++++++++++++
tools/tracing/rtla/src/timerlat_bpf.h | 59 ++++++
tools/tracing/rtla/src/timerlat_hist.c | 234 ++++++++++++++-------
tools/tracing/rtla/src/timerlat_top.c | 371 ++++++++++++++++++++++-----------
tools/tracing/rtla/src/trace.c | 4 +
tools/tracing/rtla/tests/timerlat.t | 14 ++
tools/verification/rv/Makefile.rv | 2 +-
20 files changed, 932 insertions(+), 208 deletions(-)
create mode 100644 tools/tracing/rtla/src/timerlat.bpf.c
create mode 100644 tools/tracing/rtla/src/timerlat_bpf.c
create mode 100644 tools/tracing/rtla/src/timerlat_bpf.h
next reply other threads:[~2025-03-06 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 18:18 Steven Rostedt [this message]
2025-03-06 18:18 ` [for-next][PATCH 01/10] rtla/timerlat: Unify params struct Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 02/10] tools/build: Add bpftool-skeletons feature test Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 03/10] rtla: Add optional dependency on BPF tooling Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 04/10] rtla/timerlat: Add BPF skeleton to collect samples Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 05/10] rtla/timerlat_hist: Use BPF " Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 06/10] rtla/timerlat_top: Move divisor to update Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 07/10] rtla/timerlat_top: Use BPF to collect samples Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 08/10] rtla/timerlat: Test BPF mode Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 09/10] tools/rv: Keep user LDFLAGS in build Steven Rostedt
2025-03-06 18:18 ` [for-next][PATCH 10/10] rtla: Refactor save_trace_to_file 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=20250306181801.485766945@goodmis.org \
--to=rostedt@goodmis.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglozar@redhat.com \
/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