From: Peter Zijlstra <peterz@infradead.org>
To: Jens Remus <jremus@linux.ibm.com>
Cc: Steven Rostedt <rostedt@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, x86@kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrii Nakryiko <andrii@kernel.org>,
Indu Bhagat <indu.bhagat@oracle.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
Beau Belgrave <beaub@linux.microsoft.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Florian Weimer <fweimer@redhat.com>, Sam James <sam@gentoo.org>,
Kees Cook <kees@kernel.org>,
Carlos O'Donell <codonell@redhat.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH v16 0/4] perf: Support the deferred unwinding infrastructure
Date: Fri, 24 Oct 2025 16:08:15 +0200 [thread overview]
Message-ID: <20251024140815.GE3245006@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <a59509f0-5888-4663-9e82-98e27fc3e813@linux.ibm.com>
On Fri, Oct 24, 2025 at 03:58:20PM +0200, Jens Remus wrote:
> Hello Peter!
>
> On 10/24/2025 12:41 PM, Peter Zijlstra wrote:
> > On Fri, Oct 24, 2025 at 11:29:26AM +0200, Peter Zijlstra wrote:
> >> On Thu, Oct 23, 2025 at 05:00:02PM +0200, Peter Zijlstra wrote:
> >>
> >>> Trouble is, pretty much every unwind is 510 entries long -- this cannot
> >>> be right. I'm sure there's a silly mistake in unwind/user.c but I'm too
> >>> tired to find it just now. I'll try again tomorrow.
> >>
> >> PEBKAC
> >
> > Anyway, while staring at this, I noted that the perf userspace unwind
> > code has a few bits that are missing from the new shiny thing.
> >
> > How about something like so? This add an optional arch specific unwinder
> > at the very highest priority (bit 0) and uses that to do a few extra
> > bits before disabling itself and falling back to whatever lower prio
> > unwinder to do the actual unwinding.
>
> unwind user sframe does not need any of this special handling, because
> it knows for each IP whether the SP or FP is the CFA base register
> and whether the FP and RA have been saved.
It still can't unwind VM86 stacks. But yes, it should do lots better
with that start of function hack.
> Isn't this actually specific to unwind user fp? If the IP is at
> function entry, then the FP has not been setup yet. I think unwind user
> fp could handle this using an arch specific is_uprobe_at_func_entry() to
> determine whether to use a new frame_fp_entry instead of frame_fp. For
> x86 the following frame_fp_entry should work, if I am not wrong:
>
> #define ARCH_INIT_USER_FP_ENTRY_FRAME(ws) \
> .cfa_off = 1*(ws), \
> .ra_off = -1*(ws), \
> .fp_off = 0, \
> .use_fp = false,
>
> Following roughly outlines the required changes:
>
> diff --git a/kernel/unwind/user.c b/kernel/unwind/user.c
>
> -static int unwind_user_next_fp(struct unwind_user_state *state)
> +static int unwind_user_next_common(struct unwind_user_state *state,
> + const struct unwind_user_frame *frame,
> + struct pt_regs *regs)
>
> @@ -71,6 +83,7 @@ static int unwind_user_next_common(struct unwind_user_state *state,
> state->sp = sp;
> if (frame->fp_off)
> state->fp = fp;
> + state->topmost = false;
> return 0;
> }
> @@ -154,6 +167,7 @@ static int unwind_user_start(struct unwind_user_state *state)
> state->sp = user_stack_pointer(regs);
> state->fp = frame_pointer(regs);
> state->ws = compat_user_mode(regs) ? sizeof(int) : sizeof(long);
> + state->topmost = true;
>
> return 0;
> }
>
> static int unwind_user_next_fp(struct unwind_user_state *state)
> {
> const struct unwind_user_frame fp_frame = {
> ARCH_INIT_USER_FP_FRAME(state->ws)
> };
> const struct unwind_user_frame fp_entry_frame = {
> ARCH_INIT_USER_FP_ENTRY_FRAME(state->ws)
> };
> struct pt_regs *regs = task_pt_regs(current);
>
> if (state->topmost && is_uprobe_at_func_entry(regs))
> return unwind_user_next_common(state, &fp_entry_frame, regs);
> else
> return unwind_user_next_common(state, &fp_frame, regs);
> }
>
> diff --git a/include/linux/unwind_user_types.h b/include/linux/unwind_user_types.h
> @@ -43,6 +43,7 @@ struct unwind_user_state {
> unsigned int ws;
> enum unwind_user_type current_type;
> unsigned int available_types;
> + bool topmost;
> bool done;
> };
>
> What do you think?
Yeah, I suppose that should work. Let me rework things accordingly.
next prev parent reply other threads:[~2025-10-24 14:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 21:40 [PATCH v16 0/4] perf: Support the deferred unwinding infrastructure Steven Rostedt
2025-10-07 21:40 ` [PATCH v16 1/4] unwind: Add interface to allow tracing a single task Steven Rostedt
2025-10-07 21:40 ` [PATCH v16 2/4] perf: Support deferred user callchains Steven Rostedt
2025-10-07 21:40 ` [PATCH v16 3/4] perf: Have the deferred request record the user context cookie Steven Rostedt
2025-10-07 21:40 ` [PATCH v16 4/4] perf: Support deferred user callchains for per CPU events Steven Rostedt
2025-10-23 15:00 ` [PATCH v16 0/4] perf: Support the deferred unwinding infrastructure Peter Zijlstra
2025-10-23 16:40 ` Steven Rostedt
2025-10-24 8:26 ` Peter Zijlstra
2025-10-24 12:58 ` Peter Zijlstra
2025-10-26 0:58 ` Namhyung Kim
2025-10-24 9:29 ` Peter Zijlstra
2025-10-24 10:41 ` Peter Zijlstra
2025-10-24 13:58 ` Jens Remus
2025-10-24 14:08 ` Peter Zijlstra [this message]
2025-10-24 14:51 ` Peter Zijlstra
2025-10-24 14:54 ` Peter Zijlstra
2025-10-24 14:57 ` Peter Zijlstra
2025-10-24 15:10 ` Peter Zijlstra
2025-10-24 15:09 ` Jens Remus
2025-10-24 15:11 ` Peter Zijlstra
2025-10-29 9:36 ` [tip: perf/core] unwind_user/x86: Teach FP unwind about start of function tip-bot2 for Peter Zijlstra
2025-11-04 11:22 ` [PATCH v16 0/4] perf: Support the deferred unwinding infrastructure Florian Weimer
2025-11-05 13:08 ` Peter Zijlstra
2025-10-29 9:36 ` [tip: perf/core] perf: Support deferred user unwind tip-bot2 for Peter Zijlstra
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=20251024140815.GE3245006@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=codonell@redhat.com \
--cc=fweimer@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=indu.bhagat@oracle.com \
--cc=jemarch@gnu.org \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=kees@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=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@kernel.org \
--cc=sam@gentoo.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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