[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bgnoc3j5etfi53otrrn4u23k7ly5ltyun7uhhmw5vhebsqlzgs@bl7ymu7bd74z>
Date: Sun, 4 May 2025 10:53:56 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Peter Zijlstra <peterz@...radead.org>, x86@...nel.org,
Jiri Olsa <jolsa@...nel.org>, Namhyung Kim <namhyung@...nel.org>
Subject: Re: [PATCH v7 01/17] unwind_user: Add user space unwinding API
On Sun, May 04, 2025 at 12:43:30PM -0400, Steven Rostedt wrote:
> On Sun, 4 May 2025 11:30:32 +0200
> Ingo Molnar <mingo@...nel.org> wrote:
>
> > > +struct unwind_user_state {
> > > + unsigned long ip;
> > > + unsigned long sp;
> > > + unsigned long fp;
> > > + enum unwind_user_type type;
> > > + bool done;
> > > +};
> >
> > Will any of these types be visible to tooling via ABIs?
>
> Not that I'm aware of. Josh can confirm. Josh?
>
> With the exception of BTF (which exposes pretty much all structures), I
> believe this is completely internal for the generic code of the unwinder.
Correct, these types are strictly internal to the kernel.
--
Josh
Powered by blists - more mailing lists