[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260123153247.004688f6@gandalf.local.home>
Date: Fri, 23 Jan 2026 15:32:47 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Yaxiong Tian <tianyaxiong@...inos.cn>
Cc: axboe@...nel.dk, mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] tracing: Export eval_map_wq for asynchronous use by
other modules
On Thu, 22 Jan 2026 11:24:15 +0800
Yaxiong Tian <tianyaxiong@...inos.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
Powered by blists - more mailing lists