[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250501112712.755d238c@gandalf.local.home>
Date: Thu, 1 May 2025 11:27:12 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] tracing: tprobe-events: Register tracepoint when
enable tprobe event
On Mon, 17 Mar 2025 17:03:16 +0900
"Masami Hiramatsu (Google)" <mhiramat@...nel.org> wrote:
> From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
>
> As same as fprobe, register tracepoint stub function only when enabling
> tprobe events. The major changes are introducing a list of
> tracepoint_user and its lock, and tprobe_event_module_nb, which is
> another module notifier for module loading/unloading. By spliting the
> lock from event_mutex and a module notifier for trace_fprobe, it
> solved AB-BA lock dependency issue between event_mutex and
> tracepoint_module_list_mutex.
>
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@...nel.org>
> ---
> kernel/trace/trace_fprobe.c | 382 +++++++++++++++++++++++++------------------
> 1 file changed, 218 insertions(+), 164 deletions(-)
Is this patch still needed? It doesn't apply cleanly.
-- Steve
Powered by blists - more mailing lists