lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250122111322.26eb3540@gandalf.local.home>
Date: Wed, 22 Jan 2025 11:13:22 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Josh Poimboeuf <jpoimboe@...nel.org>
Cc: x86@...nel.org, Peter Zijlstra <peterz@...radead.org>, Ingo Molnar
 <mingo@...nel.org>, Arnaldo Carvalho de Melo <acme@...nel.org>,
 linux-kernel@...r.kernel.org, Indu Bhagat <indu.bhagat@...cle.com>, Mark
 Rutland <mark.rutland@....com>, Alexander Shishkin
 <alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>,
 Namhyung Kim <namhyung@...nel.org>, Ian Rogers <irogers@...gle.com>, Adrian
 Hunter <adrian.hunter@...el.com>, linux-perf-users@...r.kernel.org, Mark
 Brown <broonie@...nel.org>, linux-toolchains@...r.kernel.org, Jordan Rome
 <jordalgo@...a.com>, Sam James <sam@...too.org>,
 linux-trace-kernel@...r.kernel.org, Andrii Nakryiko
 <andrii.nakryiko@...il.com>, Jens Remus <jremus@...ux.ibm.com>, Mathieu
 Desnoyers <mathieu.desnoyers@...icios.com>, Florian Weimer
 <fweimer@...hat.com>, Andy Lutomirski <luto@...nel.org>, Masami Hiramatsu
 <mhiramat@...nel.org>, Weinan Liu <wnliu@...gle.com>
Subject: Re: [PATCH v4 00/39] unwind, perf: sframe user space unwinding

On Tue, 21 Jan 2025 18:30:52 -0800
Josh Poimboeuf <jpoimboe@...nel.org> wrote:

> The interface is similar to {task,irq}_work.  The caller owns an
> unwind_work struct:
> 
>   struct unwind_work {
> 	struct callback_head		work;
> 	unwind_callback_t		func;
> 	int				pending;
>   };
> 
> For perf, struct unwind_work is embedded in struct perf_event.  For
> ftrace maybe it would live in task_struct?

Hmm, this is going to be difficult, as I don't want to add more to a task
struct as it's already too bloated as is. I'll have to think about this a bit.

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ