From: Gabriele Monaco <gmonaco@redhat.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Nam Cao <namcao@linutronix.de>,
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: Fri, 10 Oct 2025 15:02:42 +0200 [thread overview]
Message-ID: <0f438533d0a0189efb4649dfac3190196330868e.camel@redhat.com> (raw)
In-Reply-To: <20251010125823-9bcb33be-96b9-4753-8ae0-11576f0e8d40@linutronix.de>
On Fri, 2025-10-10 at 13:02 +0200, Thomas Weißschuh wrote:
> > So if I get it correctly, you are both "voting" for removing reactors in
> > favour
> > of tracepoint-only error reporting.
> > Am I getting this right?
>
> No, it is a suggestion for a cleanup/optimization where reactors are not
> directly called from the monitors but instead from a tracepoint which is
> triggered from the monitors. It would decouple the monitor and reactor
> subsystems.
Right, now I understand this better. Interesting idea, we can give it a thought.
Thanks,
Gabriele
next prev parent reply other threads:[~2025-10-10 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 10:49 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
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 [this message]
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=0f438533d0a0189efb4649dfac3190196330868e.camel@redhat.com \
--to=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=namcao@linutronix.de \
--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
all inboxes | Powered by JetHome®