From: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
To: <rostedt@goodmis.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <mark-pk.tsai@mediatek.com>,
<matthias.bgg@gmail.com>, <mingo@redhat.com>,
<yj.chiang@mediatek.com>
Subject: Re: [PATCH v3 1/2] tracing: Avoid adding tracer option before update_tracer_options
Date: Tue, 26 Apr 2022 16:17:06 +0800 [thread overview]
Message-ID: <20220426081706.13274-1-mark-pk.tsai@mediatek.com> (raw)
In-Reply-To: <20220422174258.1f41777a@gandalf.local.home>
> > To prepare for support asynchronous tracer_init_tracefs initcall,
> > avoid calling create_trace_option_files before __update_tracer_options.
> > Otherwise, create_trace_option_files will show warning because
> > some tracers in trace_types list are already in tr->topts.
> >
> > For example, hwlat_tracer call register_tracer in late_initcall,
> > and global_trace.dir is already created in tracing_init_dentry,
> > hwlat_tracer will be put into tr->topts.
> > Then if the __update_tracer_options is executed after hwlat_tracer
> > registered, create_trace_option_files find that hwlat_tracer is
> > already in tr->topts.
> >
> > Link: https://lore.kernel.org/lkml/20220322133339.GA32582@xsang-OptiPlex-9020/
> > Reported-by: kernel test robot <oliver.sang@intel.com>
> > Signed-off-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
>
> Before this patch:
>
> # ls /sys/kernel/tracing/options
> annotate funcgraph-duration hex stacktrace
> bin funcgraph-irqs irq-info sym-addr
> blk_cgname funcgraph-overhead latency-format sym-offset
> blk_cgroup funcgraph-overrun markers sym-userobj
> blk_classic funcgraph-proc overwrite test_nop_accept
> block funcgraph-tail pause-on-trace test_nop_refuse
> context-info func-no-repeats printk-msg-only trace_printk
> disable_on_free func_stack_trace print-parent userstacktrace
> display-graph function-fork raw verbose
> event-fork function-trace record-cmd
> funcgraph-abstime graph-time record-tgid
> funcgraph-cpu hash-ptr sleep-time
>
>
> After this patch:
>
> # ls /sys/kernel/tracing/options
> annotate disable_on_free irq-info raw trace_printk
> bin display-graph latency-format record-cmd userstacktrace
> blk_cgname event-fork markers record-tgid verbose
> blk_cgroup function-fork overwrite stacktrace
> blk_classic function-trace pause-on-trace sym-addr
> block hash-ptr printk-msg-only sym-offset
> context-info hex print-parent sym-userobj
>
> Not good.
Calling __update_tracer_options() when tracer_options_updated=false have no
effect because it return directly in add_tracer_options().
I will fix it in v4 as you suggest in the below comment.
>
> > ---
> > kernel/trace/trace.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> > index eb44418574f9..85ec758c4455 100644
> > --- a/kernel/trace/trace.c
> > +++ b/kernel/trace/trace.c
> > @@ -6317,12 +6317,18 @@ static void tracing_set_nop(struct trace_array *tr)
> > tr->current_trace = &nop_trace;
> > }
> >
> > +static bool tracer_options_updated;
> > +
> > static void add_tracer_options(struct trace_array *tr, struct tracer *t)
> > {
> > /* Only enable if the directory has been created already. */
> > if (!tr->dir)
> > return;
> >
> > + /* Only create trace option files after update_tracer_options finish */
> > + if (!tracer_options_updated)
> > + return;
> > +
> > create_trace_option_files(tr, t);
> > }
> >
> > @@ -9133,6 +9139,7 @@ static void update_tracer_options(struct trace_array *tr)
> > {
> > mutex_lock(&trace_types_lock);
> > __update_tracer_options(tr);
> > + tracer_options_updated = true;
>
> I think you want to set this before the __update, as doing it after just
> makes the update a nop.
You are right.
I will update in v4, thanks!
>
> -- Steve
>
>
> > mutex_unlock(&trace_types_lock);
> > }
> >
next prev parent reply other threads:[~2022-04-26 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 15:22 [PATCH v3 0/2] tracing: make tracer_init_tracefs initcall asynchronous Mark-PK Tsai
2022-03-23 15:22 ` [PATCH v3 1/2] tracing: Avoid adding tracer option before update_tracer_options Mark-PK Tsai
2022-04-22 21:42 ` Steven Rostedt
2022-04-26 8:17 ` Mark-PK Tsai [this message]
2022-03-23 15:22 ` [PATCH v3 2/2] tracing: make tracer_init_tracefs initcall asynchronous Mark-PK Tsai
2022-04-22 22:07 ` Steven Rostedt
2022-04-26 8:05 ` Mark-PK Tsai
2022-04-22 9:27 ` [PATCH v3 0/2] " Mark-PK Tsai
2022-04-22 15:41 ` Steven Rostedt
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=20220426081706.13274-1-mark-pk.tsai@mediatek.com \
--to=mark-pk.tsai@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yj.chiang@mediatek.com \
/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®