From: Steven Rostedt <rostedt@goodmis.org>
To: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Cc: <mingo@redhat.com>, <matthias.bgg@gmail.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <yj.chiang@mediatek.com>
Subject: Re: [PATCH v3 2/2] tracing: make tracer_init_tracefs initcall asynchronous
Date: Fri, 22 Apr 2022 18:07:34 -0400 [thread overview]
Message-ID: <20220422180734.225718b7@gandalf.local.home> (raw)
In-Reply-To: <20220323152257.7871-3-mark-pk.tsai@mediatek.com>
On Wed, 23 Mar 2022 23:22:57 +0800
Mark-PK Tsai <mark-pk.tsai@mediatek.com> wrote:
> +static __init int tracer_init_tracefs(void)
> +{
> + int ret;
> +
> + trace_access_lock_init();
> +
> + ret = tracing_init_dentry();
> + if (ret)
> + return 0;
> +
> + INIT_WORK(&tracerfs_init_work, tracer_init_tracefs_work_func);
> + if (!eval_map_wq)
> + tracer_init_tracefs_work_func(&tracerfs_init_work);
Why go through the bother of doing the INIT_WORK if eval_map_wq is not
created? Just do:
if (eval_map_wq) {
INIT_WORK(&tracerfs_init_work, tracer_init_tracefs_work_func);
queue_work(eval_map_wq, &tracerfs_init_work);
} else {
tracer_init_tracefs_work_func(NULL);
}
But that's just a nit anyway.
-- Steve
> + else
> + queue_work(eval_map_wq, &tracerfs_init_work);
>
> return 0;
> }
next prev parent reply other threads:[~2022-04-22 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 15:22 [PATCH v3 0/2] " 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
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 [this message]
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=20220422180734.225718b7@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mingo@redhat.com \
--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®