From: Gabriele Monaco <gmonaco@redhat.com>
To: Nam Cao <namcao@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] rv: Remove the nop reactor
Date: Mon, 21 Jul 2025 12:29:24 +0200 [thread overview]
Message-ID: <feae7a189afa69091816074dcf66a496b11bdd38.camel@redhat.com> (raw)
In-Reply-To: <21a530ffb705887d7aed18255572521e5b880bc0.1753091084.git.namcao@linutronix.de>
On Mon, 2025-07-21 at 11:47 +0200, Nam Cao wrote:
> As suggested by the name, the nop reactor does not do anything. It is
> the
> default reactor when nothing else is selected.
>
> However, the monitors already null-check the reactor function
> pointers.
> Thus, instead of a nop reactor, just set the react function pointer
> to
> NULL. The nop reactor can then be removed.
>
> Signed-off-by: Nam Cao <namcao@linutronix.de>
Thanks for the patch, I'd need to go through this a bit more in detail.
As far as I remember, the only way to disable reaction is to set it to
the nop reactor.
With your patch the behaviour changes and, to disable the reactor, you
now need to write an empty string, this should be documented somewhere,
at the very least. Perhaps userspace tools (tools/verification/rv)
might break and would need adaptation.
We could still remove the kernel side implementation, but from
userspace (tracefs) we might want to keep the nop reactor available,
setting it would set the reactor to NULL under the hood.
If you really want to change also the user space interface, we might
want to imitate other tracefs features and use something like printk /
!printk to enable/disable a reactor.
What do you think? Did I miss anything here?
Thanks,
Gabriele
> ---
> kernel/trace/rv/rv_reactors.c | 63 ++++++---------------------------
> --
> 1 file changed, 11 insertions(+), 52 deletions(-)
>
> diff --git a/kernel/trace/rv/rv_reactors.c
> b/kernel/trace/rv/rv_reactors.c
> index a8e849e6cd85..aee622e4b833 100644
> --- a/kernel/trace/rv/rv_reactors.c
> +++ b/kernel/trace/rv/rv_reactors.c
> @@ -70,17 +70,6 @@
> */
> static LIST_HEAD(rv_reactors_list);
>
> -static struct rv_reactor *get_reactor_rdef_by_name(char *name)
> -{
> - struct rv_reactor *r;
> -
> - list_for_each_entry(r, &rv_reactors_list, list) {
> - if (strcmp(name, r->name) == 0)
> - return r;
> - }
> - return NULL;
> -}
> -
> /*
> * Available reactors seq functions.
> */
> @@ -174,7 +163,7 @@ static void monitor_swap_reactors_single(struct
> rv_monitor *mon,
>
> mon->reactor = reactor;
> mon->reacting = reacting;
> - mon->react = reactor->react;
> + mon->react = reactor ? reactor->react : NULL;
>
> /* enable only once if iterating through a container */
> if (monitor_enabled && !nested)
> @@ -210,10 +199,15 @@ monitor_reactors_write(struct file *file, const
> char __user *user_buf,
> struct rv_reactor *reactor;
> struct seq_file *seq_f;
> int retval = -EINVAL;
> - bool enable;
> char *ptr;
> int len;
>
> + /*
> + * See monitor_reactors_open()
> + */
> + seq_f = file->private_data;
> + mon = seq_f->private;
> +
> if (count < 1 || count > MAX_RV_REACTOR_NAME_SIZE + 1)
> return -EINVAL;
>
> @@ -226,14 +220,10 @@ monitor_reactors_write(struct file *file, const
> char __user *user_buf,
> ptr = strim(buff);
>
> len = strlen(ptr);
> - if (!len)
> + if (!len) {
> + monitor_swap_reactors(mon, NULL, false);
> return count;
> -
> - /*
> - * See monitor_reactors_open()
> - */
> - seq_f = file->private_data;
> - mon = seq_f->private;
> + }
>
> mutex_lock(&rv_interface_lock);
>
> @@ -243,12 +233,7 @@ monitor_reactors_write(struct file *file, const
> char __user *user_buf,
> if (strcmp(ptr, reactor->name) != 0)
> continue;
>
> - if (strcmp(reactor->name, "nop"))
> - enable = false;
> - else
> - enable = true;
> -
> - monitor_swap_reactors(mon, reactor, enable);
> + monitor_swap_reactors(mon, reactor, true);
>
> retval = count;
> break;
> @@ -435,32 +420,12 @@ int reactor_populate_monitor(struct rv_monitor
> *mon)
> if (!tmp)
> return -ENOMEM;
>
> - /*
> - * Configure as the rv_nop reactor.
> - */
> - mon->reactor = get_reactor_rdef_by_name("nop");
> - mon->reacting = false;
> -
> return 0;
> }
>
> -/*
> - * Nop reactor register
> - */
> -__printf(1, 2) static void rv_nop_reaction(const char *msg, ...)
> -{
> -}
> -
> -static struct rv_reactor rv_nop = {
> - .name = "nop",
> - .description = "no-operation reactor: do nothing.",
> - .react = rv_nop_reaction
> -};
> -
> int init_rv_reactors(struct dentry *root_dir)
> {
> struct dentry *available, *reacting;
> - int retval;
>
> available = rv_create_file("available_reactors",
> RV_MODE_READ, root_dir, NULL,
> &available_reactors_ops);
> @@ -471,16 +436,10 @@ int init_rv_reactors(struct dentry *root_dir)
> if (!reacting)
> goto rm_available;
>
> - retval = __rv_register_reactor(&rv_nop);
> - if (retval)
> - goto rm_reacting;
> -
> turn_reacting_on();
>
> return 0;
>
> -rm_reacting:
> - rv_remove(reacting);
> rm_available:
> rv_remove(available);
> out_err:
next prev parent reply other threads:[~2025-07-21 10:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 9:47 [PATCH 0/6] rv: Clean up & simplify Nam Cao
2025-07-21 9:47 ` [PATCH 1/6] rv: Remove unused field in struct rv_monitor_def Nam Cao
2025-07-21 13:01 ` Gabriele Monaco
2025-07-21 9:47 ` [PATCH 2/6] rv: Merge struct rv_monitor_def into struct rv_monitor Nam Cao
2025-07-21 14:13 ` Gabriele Monaco
2025-07-21 9:47 ` [PATCH 3/6] rv: Merge struct rv_reactor_def into struct rv_reactor Nam Cao
2025-07-21 14:29 ` Gabriele Monaco
2025-07-21 9:47 ` [PATCH 4/6] rv: Remove rv_reactor's reference counter Nam Cao
2025-07-21 13:20 ` Gabriele Monaco
2025-07-21 14:04 ` Nam Cao
2025-07-21 15:49 ` Gabriele Monaco
2025-07-22 8:27 ` Nam Cao
2025-07-22 8:30 ` Gabriele Monaco
2025-07-21 9:47 ` [PATCH 5/6] rv: Remove the nop reactor Nam Cao
2025-07-21 10:29 ` Gabriele Monaco [this message]
2025-07-21 14:10 ` Nam Cao
2025-07-21 9:47 ` [PATCH 6/6] rv: Remove struct rv_monitor::reacting Nam Cao
2025-07-21 14:38 ` Gabriele Monaco
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=feae7a189afa69091816074dcf66a496b11bdd38.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 \
/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;
as well as URLs for NNTP newsgroup(s).