From: Steven Rostedt <rostedt@goodmis.org>
To: Yaxiong Tian <tianyaxiong@kylinos.cn>
Cc: axboe@kernel.dk, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] tracing: Export eval_map_wq for asynchronous use by other modules
Date: Fri, 23 Jan 2026 15:32:47 -0500 [thread overview]
Message-ID: <20260123153247.004688f6@gandalf.local.home> (raw)
In-Reply-To: <20260122032415.395548-1-tianyaxiong@kylinos.cn>
On Thu, 22 Jan 2026 11:24:15 +0800
Yaxiong Tian <tianyaxiong@kylinos.cn> wrote:
> The eval_map_work_func() function, though queued in eval_map_wq,
> holds the trace_event_sem read-write lock for a long time during
> kernel boot. This causes blocking issues for other functions.
>
> Making eval_map_wq extern allows other modules to schedule their
> work asynchronously on this queue, preventing it from blocking
> the main boot thread.
If you are going to make this wq generic for other parts of the tracing
code, then let's rename it. As "eval_map" is specific to the enum mappings
being updated (which I hope someday I can get that update working at build
time. And when I do, the name will be totally meaningless).
Let's rename it to "trace_init_wq" instead.
-- Steve
next prev parent reply other threads:[~2026-01-23 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 3:20 [PATCH 0/3] Tracing: Accelerate Kernel Boot by Asynchronizing Yaxiong Tian
2026-01-22 3:24 ` [PATCH 1/3] tracing: Export eval_map_wq for asynchronous use by other modules Yaxiong Tian
2026-01-23 20:32 ` Steven Rostedt [this message]
2026-01-26 2:45 ` Yaxiong Tian
2026-01-22 3:24 ` [PATCH 2/3] tracing/kprobes: Make setup_boot_kprobe_events() asynchronous Yaxiong Tian
2026-01-22 3:24 ` [PATCH 3/3] blktrace: Make init_blk_tracer() asynchronous Yaxiong Tian
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=20260123153247.004688f6@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=tianyaxiong@kylinos.cn \
/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