From: Crystal Wood <crwood@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
John Kacur <jkacur@redhat.com>,
Luis Goncalves <lgoncalv@redhat.com>,
Costa Shulyupin <costa.shul@redhat.com>,
Wander Lairson Costa <wander@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH v3 0/7] rtla/timerlat: Add --bpf-action option
Date: Fri, 31 Oct 2025 09:49:08 -0400 [thread overview]
Message-ID: <a0e34d41214dd6d98e3c7b7ec37be7ad0e1812e0.camel@redhat.com> (raw)
In-Reply-To: <20251027153401.1039217-1-tglozar@redhat.com>
On Mon, 2025-10-27 at 16:33 +0100, Tomas Glozar wrote:
> This patchset extends rtla-timerlat's BPF support with the option of
> executing a user-supplied BPF program on latency threshold overflow.
>
> See the supplied example and documentation for how to create a program.
> bpf_tail_call() is used to chain the program with the built-in BPF
> sample collection program, if the threshold is hit.
>
> The feature can be used for both in-kernel data collection and sending
> signals to userspace directly from the kernel, if the kernel version
> allows it.
>
> Note: The patchset will have to be rebased on top of [1], or vice versa,
> since they both touch stop_tracing() ([1] adds one call of it, and this
> patchset adds an extra argument to it).
Probably best to add an updated version of that patch to this patchset.
> v3 changes:
> - Add tests/bpf/bpf_action_map.c to test commit (forgot to run
> git add before).
Might be nice to build that as part of "all", for the sake of people
running the tests directly (FWIW, I still don't see anything in the
makefile or engine.sh documenting how to satisfy that dependency).
In any case:
Reviewed-by: Crystal Wood <crwood@redhat.com>
-Crystal
prev parent reply other threads:[~2025-10-31 13:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 15:33 Tomas Glozar
2025-10-27 15:33 ` [PATCH v3 1/7] rtla/timerlat: Support tail call from BPF program Tomas Glozar
2025-11-03 14:23 ` Wander Lairson Costa
2025-11-25 13:35 ` Tomas Glozar
2025-10-27 15:33 ` [PATCH v3 2/7] rtla/timerlat: Add --bpf-action option Tomas Glozar
2025-11-03 14:44 ` Wander Lairson Costa
2025-11-25 13:48 ` Tomas Glozar
2025-11-25 18:10 ` Wander Lairson Costa
2025-10-27 15:33 ` [PATCH v3 3/7] rtla/timerlat: Add example for BPF action program Tomas Glozar
2025-10-27 15:33 ` [PATCH v3 4/7] rtla/tests: Test " Tomas Glozar
2025-11-03 15:10 ` Wander Lairson Costa
2025-11-03 15:17 ` Tomas Glozar
2025-10-27 15:33 ` [PATCH v3 5/7] rtla/tests: Run Test::Harness in verbose mode Tomas Glozar
2025-11-03 15:11 ` Wander Lairson Costa
2025-10-27 15:34 ` [PATCH v3 6/7] Documentation/rtla: Rename sample/ to example/ Tomas Glozar
2025-11-03 13:41 ` Wander Lairson Costa
2025-10-27 15:34 ` [PATCH v3 7/7] Documentation/rtla: Document --bpf-action option Tomas Glozar
2025-11-03 13:44 ` Wander Lairson Costa
2025-10-31 13:49 ` Crystal Wood [this message]
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=a0e34d41214dd6d98e3c7b7ec37be7ad0e1812e0.camel@redhat.com \
--to=crwood@redhat.com \
--cc=acme@kernel.org \
--cc=costa.shul@redhat.com \
--cc=jkacur@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.com \
--cc=wander@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
all inboxes | Powered by JetHome®