From: Valentin Schneider <vschneid@redhat.com>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Tomas Glozar <tglozar@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Costa Shulyupin <costa.shul@redhat.com>,
Crystal Wood <crwood@redhat.com>, John Kacur <jkacur@redhat.com>,
Ivan Pravdin <ipravdin.official@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH v3 4/6] rtla/osnoise: Allow IPI filters to gracefully fail
Date: Wed, 15 Jul 2026 17:45:49 +0200 [thread overview]
Message-ID: <20260715154553.2020891-5-vschneid@redhat.com> (raw)
In-Reply-To: <20260715154553.2020891-1-vschneid@redhat.com>
Kernels pre v6.6 won't have:
39f7c41c908b ("tracing/filters: Enable filtering a cpumask field by another cpumask")
and thus won't be able to filter events using a user-provided cpumask, but
will still be capable of recording IPI events.
Make failing to set a filter for IPI events an acceptable error and fall
back to event handlers that do the filtering job themselves.
Suggested-by: Tomas Glozar <tglozar@redhat.com>
Signed-off-by: Valentin Schneider <vschneid@redhat.com>
---
tools/tracing/rtla/src/osnoise_top.c | 49 +++++++++++++++++++++++++---
1 file changed, 45 insertions(+), 4 deletions(-)
diff --git a/tools/tracing/rtla/src/osnoise_top.c b/tools/tracing/rtla/src/osnoise_top.c
index 353b435fefcf8..afab2f341a1e9 100644
--- a/tools/tracing/rtla/src/osnoise_top.c
+++ b/tools/tracing/rtla/src/osnoise_top.c
@@ -313,6 +313,30 @@ osnoise_ipi_cpu_handler(struct trace_seq *s, struct tep_record *record,
return 0;
}
+/*
+ * osnoise_ipi_cpu_unfiltered_handler - this is the handler for single CPU IPI
+ * events. Slightly less optimized than
+ * the filtered variant.
+ */
+static int
+osnoise_ipi_cpu_unfiltered_handler(struct trace_seq *s, struct tep_record *record,
+ struct tep_event *event, void *context)
+{
+ struct osnoise_tool *tool;
+ unsigned long long dst_cpu;
+ struct osnoise_params *params;
+ struct trace_instance *trace = context;
+
+ tool = container_of(trace, struct osnoise_tool, trace);
+ params = to_osnoise_params(tool->params);
+ tep_get_field_val(s, event, "cpu", record, &dst_cpu, 1);
+
+ if (CPU_ISSET(dst_cpu, ¶ms->common.monitored_cpus))
+ account_ipi(tool, dst_cpu);
+
+ return 0;
+}
+
static cpu_set_t cpumask_tmp_cpus;
/*
@@ -343,7 +367,7 @@ osnoise_ipi_cpumask_handler(struct trace_seq *s, struct tep_record *record,
}
/*
- * Despite already filtering for such an intersection, we need to compute
+ * Even if already filtering for such an intersection, we need to compute
* the intersection here as the @cpumask field may contain non-monitored
* CPUs.
*/
@@ -368,6 +392,7 @@ osnoise_ipi_cpumask_handler(struct trace_seq *s, struct tep_record *record,
*/
struct osnoise_tool *osnoise_init_top(struct common_params *params)
{
+ bool ipi_filters_enabled = false;
struct osnoise_tool *tool;
int retval;
@@ -402,6 +427,8 @@ struct osnoise_tool *osnoise_init_top(struct common_params *params)
/*
* If tracing on a subset of possible CPUs, leverage the kernel filtering
* infrastructure to only generate events on traced CPUs.
+ * Older kernels (pre v6.6) may have the IPI events but not the ability
+ * to filter them, so allow that to fail gracefully.
*/
if (params->cpus) {
char filter[MAX_PATH];
@@ -411,8 +438,8 @@ struct osnoise_tool *osnoise_init_top(struct common_params *params)
"ipi", "ipi_send_cpu", "filter",
filter);
if (retval < 0) {
- err_msg("Could not set ipi_send_cpu CPU filter\n");
- goto out_err;
+ debug_msg("Could not set ipi_send_cpu CPU filter\n");
+ goto no_filter;
}
@@ -421,13 +448,27 @@ struct osnoise_tool *osnoise_init_top(struct common_params *params)
"ipi", "ipi_send_cpumask", "filter",
filter);
if (retval < 0) {
+ /*
+ * If we managed to set up the previous filter but not
+ * this one, something's really wrong
+ */
err_msg("Could not set ipi_send_cpumask CPU filter\n");
goto out_err;
}
+
+ ipi_filters_enabled = true;
}
+no_filter:
+ /*
+ * If no filtering is available and we're tracing all CPUs, we can still
+ * use the filtered callback since stats are collected for all CPUs.
+ */
tep_register_event_handler(tool->trace.tep, -1, "ipi", "ipi_send_cpu",
- osnoise_ipi_cpu_handler, NULL);
+ (!params->cpus || ipi_filters_enabled) ?
+ osnoise_ipi_cpu_handler :
+ osnoise_ipi_cpu_unfiltered_handler,
+ NULL);
tep_register_event_handler(tool->trace.tep, -1, "ipi", "ipi_send_cpumask",
osnoise_ipi_cpumask_handler, NULL);
--
2.55.0
next prev parent reply other threads:[~2026-07-15 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 15:45 [PATCH v3 0/6] tracing/osnoise: Track IPIs Valentin Schneider
2026-07-15 15:45 ` [PATCH v3 1/6] rtla/osnoise: Add IPI tracking cmdline option Valentin Schneider
2026-07-15 15:45 ` [PATCH v3 2/6] rtla/osnoise: Record IPI count in osnoise top Valentin Schneider
2026-07-15 15:45 ` [PATCH v3 3/6] rtla/osnoise: Leverage IPI event filters when tracing a subset of CPUs Valentin Schneider
2026-07-15 15:45 ` Valentin Schneider [this message]
2026-07-15 15:45 ` [PATCH v3 5/6] rtla: Unconditionally clean any pre-existing filters for user-provided events Valentin Schneider
2026-07-15 15:45 ` [PATCH v3 6/6] rtla/osnoise: Trace IPI events when recording a trace file Valentin Schneider
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=20260715154553.2020891-5-vschneid@redhat.com \
--to=vschneid@redhat.com \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=crwood@redhat.com \
--cc=ipravdin.official@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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