From: Nam Cao <namcao@linutronix.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Gabriele Monaco" <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] rv: Add signal reactor
Date: Thu, 02 Oct 2025 16:56:09 +0200 [thread overview]
Message-ID: <87ikgxqrna.fsf@yellow.woof> (raw)
In-Reply-To: <6a5fde33-b3e3-44e2-8ea5-5f4cf350cf35@linutronix.de>
Thomas Weißschuh <thomas.weissschuh@linutronix.de> writes:
> I am wondering if it would make sense to add a new tracepoint that
> fires in addition of the reactors. That would allow multiple
> simultaneous consumers and also bespoke handlers in userspace.
We do have tracepoints for each monitor in: kernel/trace/rv/rv_trace.h
And yeah, I think it is a nice idea for all the consumers to use these
tracepoints intead (that includes rtapp testing, and also the existing
reactors). It would simplify things, as the monitors do not have to
worry about the reactors, they only need to invoke tracepoints.
But this also makes me think about the necessity of the existing
reactors. What do they offer that tracepoints do not? Myself I almost
never use the reactors, so I'm thinking about removing them. But maybe
@Gabriele has objections?
Nam
next prev parent reply other threads:[~2025-10-02 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 10:49 [PATCH] rv: Add signal reactor Thomas Weißschuh
2025-09-19 12:26 ` Gabriele Monaco
2025-09-22 16:29 ` Nam Cao
2025-09-23 7:42 ` Gabriele Monaco
2025-09-25 14:39 ` Thomas Weißschuh
2025-10-02 14:56 ` Nam Cao [this message]
2025-10-03 6:30 ` Gabriele Monaco
2025-10-06 10:10 ` Thomas Weißschuh
2025-10-06 15:19 ` Gabriele Monaco
2025-10-10 11:02 ` Thomas Weißschuh
2025-10-10 13:02 ` Gabriele Monaco
2025-10-10 12:12 ` Nam Cao
2025-09-30 14:18 ` Thomas Weißschuh
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=87ikgxqrna.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=gmonaco@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=thomas.weissschuh@linutronix.de \
/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