From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vineet Gupta <vineet.gupta@linux.dev>,
mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, andrii@kernel.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@meta.com,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing: fgraph: Raise FTRACE_RETSTACK_ALLOC_SIZE to 1024
Date: Sat, 26 Sep 2026 08:46:47 -0400 [thread overview]
Message-ID: <20260926084647.3685ae85@fedora> (raw)
In-Reply-To: <20260924100040.GD4121339@noisy.programming.kicks-ass.net>
On Thu, 24 Sep 2026 12:00:40 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
>
> Does this work?
>
> diff --git a/kernel/trace/fgraph.c b/kernel/trace/fgraph.c
> index ed455b53513b..155dafad474d 100644
> --- a/kernel/trace/fgraph.c
> +++ b/kernel/trace/fgraph.c
> @@ -1036,10 +1036,9 @@ trace_func_graph_ent_t ftrace_graph_entry = ftrace_graph_entry_stub;
> /* Try to assign a return stack array on FTRACE_RETSTACK_ALLOC_SIZE tasks. */
> static int alloc_retstack_tasklist(unsigned long **ret_stack_list)
> {
> - int i;
> - int ret = 0;
> int start = 0, end = FTRACE_RETSTACK_ALLOC_SIZE;
> struct task_struct *g, *t;
> + int i, ret = 0;
>
> if (WARN_ON_ONCE(!fgraph_stack_cachep))
> return -ENOMEM;
> @@ -1054,26 +1053,29 @@ static int alloc_retstack_tasklist(unsigned long **ret_stack_list)
> }
> }
>
> - rcu_read_lock();
> - for_each_process_thread(g, t) {
> - if (start == end) {
> - ret = -EAGAIN;
> - goto unlock;
> - }
> + scoped_guard (rcu) {
> + for_each_process_thread(g, t) {
> + unsigned long *rs;
> +
> + if (t->ret_stack)
> + continue;
> +
> + rs = kmem_cache_alloc(fgraph_stack_cachep, GFP_NOWAIT);
> + if (!rs) {
> + if (start == end)
> + return -EAGAIN;
> + rs = ret_stack_list[start++];
> + }
Yeah this is fine. This iteration code goes back to when function graph
was first added back in 2008. Back then, looping all tasks required
taking the task_list lock and I remember we didn't want to call
kmalloc() while holding that. This code could definitely use some
reassessment.
-- Steve
>
> - if (t->ret_stack == NULL) {
> atomic_set(&t->trace_overrun, 0);
> - ret_stack_init_task_vars(ret_stack_list[start]);
> + ret_stack_init_task_vars(rs);
> t->curr_ret_stack = 0;
> t->curr_ret_depth = -1;
> /* Make sure the tasks see the 0 first: */
> - smp_wmb();
> - t->ret_stack = ret_stack_list[start++];
> + smp_store_release(&t->ret_stack, rs);
> }
> }
>
> -unlock:
> - rcu_read_unlock();
> free:
> for (i = start; i < end; i++)
> kmem_cache_free(fgraph_stack_cachep, ret_stack_list[i]);
next prev parent reply other threads:[~2026-09-26 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 22:55 [PATCH 0/2] tracing: fgraph: cut the cost of the shadow stack retry loop Vineet Gupta
2026-09-22 22:55 ` [PATCH 1/2] tracing: fgraph: Raise FTRACE_RETSTACK_ALLOC_SIZE to 1024 Vineet Gupta
2026-09-24 10:00 ` Peter Zijlstra
2026-09-25 19:32 ` Vineet Gupta
2026-09-26 12:46 ` Steven Rostedt [this message]
2026-09-22 22:55 ` [PATCH 2/2] tracing: fgraph: Add a cond_resched() to the shadow stack retry loop Vineet Gupta
2026-09-23 8:47 ` Steven Rostedt
2026-09-24 20:45 ` [PATCH 0/2] tracing: fgraph: cut the cost of " Steven Rostedt
2026-09-25 2:31 ` Vineet Gupta
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=20260926084647.3685ae85@fedora \
--to=rostedt@goodmis.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=vineet.gupta@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
all inboxes | Powered by JetHome®