From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: Show the tracer options in boot-time created instance
Date: Wed, 19 Nov 2025 09:06:02 +0900 [thread overview]
Message-ID: <20251119090602.7605a36b3fbc9184abad7a59@kernel.org> (raw)
In-Reply-To: <20251118133434.67def626@gandalf.local.home>
On Tue, 18 Nov 2025 13:34:34 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 18 Nov 2025 16:49:50 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
>
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >
> > Since tracer_init_tracefs_work_func() only updates the tracer options
> > for the global_trace, the instances created by the kernel cmdline
> > do not have those options.
> >
> > Fix to update tracer options for those boot-time created instances
> > to show those options.
> >
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > Fixes: f20a580627f43 ("ftrace: Allow instances to use function tracing")
>
> Actually, I think this should be:
>
> Fixes: 428add559b69 ("tracing: Have tracer option be instance specific")
>
> As it broke when we made function tracer options no longer global.
>
OK, let me change it.
> > ---
> > kernel/trace/trace.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> > index 8ae95800592d..2e87060e1d5a 100644
> > --- a/kernel/trace/trace.c
> > +++ b/kernel/trace/trace.c
> > @@ -10903,6 +10903,7 @@ static struct notifier_block trace_module_nb = {
> >
> > static __init void tracer_init_tracefs_work_func(struct work_struct *work)
> > {
> > + struct trace_array *tr;
> >
> > event_trace_init();
> >
> > @@ -10937,7 +10938,8 @@ static __init void tracer_init_tracefs_work_func(struct work_struct *work)
> >
> > create_trace_instances(NULL);
> >
> > - update_tracer_options(&global_trace);
> > + list_for_each_entry(tr, &ftrace_trace_arrays, list)
> > + update_tracer_options(tr);
> > }
> >
> > static __init int tracer_init_tracefs(void)
>
> Since update_trace_options() is only called by this function, instead of
> doing the loop here, change the function to be:
>
> static __init void update_tracer_options(void)
> {
> struct trace_array *tr;
>
> guard(mutex)(&trace_types_lock);
> tracer_options_updated = true;
> list_for_each_entry(tr, &ftrace_trace_arrays, list)
> __update_tracer_options(tr);
> }
OK. Let me send v2.
Thanks,
>
> Thanks,
>
> -- Steve
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2025-11-19 0:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 7:49 [PATCH] tracing: Show the tracer options in boot-time created instance Masami Hiramatsu (Google)
2025-11-18 18:34 ` Steven Rostedt
2025-11-19 0:06 ` Masami Hiramatsu [this message]
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=20251119090602.7605a36b3fbc9184abad7a59@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--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).