public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: "Gabriele Monaco" <gmonaco@redhat.com>,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
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: Fri, 10 Oct 2025 14:12:12 +0200	[thread overview]
Message-ID: <87o6qfx8f7.fsf@yellow.woof> (raw)
In-Reply-To: <2536a7777eb54ede40a335fa4204e87301b13040.camel@redhat.com>

Gabriele Monaco <gmonaco@redhat.com> writes:
> 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, I just do not use the reactors much myself and wouldn't care if they
get removed. But if they are useful for you, let's keep it.

But I do like Thomas's proposal to build the reactors on top of the
tracepoints, so that they are decoupled from the monitors.

Nam

  parent reply	other threads:[~2025-10-10 12:12 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
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 [this message]
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=87o6qfx8f7.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