From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: sunliming@linux.dev
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
sunliming <sunliming@kylinos.cn>
Subject: Re: [PATCH v2] tracing: kprobe-event: Return directly when trace kprobes is empty
Date: Wed, 28 Jan 2026 11:59:43 +0900 [thread overview]
Message-ID: <20260128115943.a752b539ba787c726bbabdfb@kernel.org> (raw)
In-Reply-To: <20260127053848.108473-1-sunliming@linux.dev>
On Tue, 27 Jan 2026 13:38:48 +0800
sunliming@linux.dev wrote:
> From: sunliming <sunliming@kylinos.cn>
>
> In enable_boot_kprobe_events(), it returns directly when trace kprobes is
> empty, thereby reducing the function's execution time. This function may
> otherwise wait for the event_mutex lock for tens of milliseconds on certain
> machines, which is unnecessary when trace kprobes is empty.
>
> Signed-off-by: sunliming <sunliming@kylinos.cn>
Looks good to me. Let me pick it.
Thanks,
> ---
> v2:
> - wrap the the null check for the dyn_event_list with macro trace_kprobe_list_empty
> ---
> kernel/trace/trace_kprobe.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> index 9953506370a5..95f2c42603d5 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -82,6 +82,7 @@ static struct trace_kprobe *to_trace_kprobe(struct dyn_event *ev)
> #define for_each_trace_kprobe(pos, dpos) \
> for_each_dyn_event(dpos) \
> if (is_trace_kprobe(dpos) && (pos = to_trace_kprobe(dpos)))
> +#define trace_kprobe_list_empty() list_empty(&dyn_event_list)
>
> static nokprobe_inline bool trace_kprobe_is_return(struct trace_kprobe *tk)
> {
> @@ -1982,6 +1983,9 @@ static __init void enable_boot_kprobe_events(void)
> struct trace_kprobe *tk;
> struct dyn_event *pos;
>
> + if (trace_kprobe_list_empty())
> + return;
> +
> guard(mutex)(&event_mutex);
> for_each_trace_kprobe(tk, pos) {
> list_for_each_entry(file, &tr->events, list)
> --
> 2.25.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-01-28 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 5:38 [PATCH v2] tracing: kprobe-event: Return directly when trace kprobes is empty sunliming
2026-01-28 2:59 ` Masami Hiramatsu [this message]
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=20260128115943.a752b539ba787c726bbabdfb@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=sunliming@kylinos.cn \
--cc=sunliming@linux.dev \
/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