From: Steven Rostedt <rostedt@goodmis.org>
To: Jens Remus <jremus@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, x86@kernel.org,
Indu Bhagat <indu.bhagat@oracle.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrii Nakryiko <andrii@kernel.org>,
"Jose E. Marchesi" <jemarch@gnu.org>,
Beau Belgrave <beaub@linux.microsoft.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>, Florian Weimer <fweimer@redhat.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH v7 00/12] unwind_deferred: Implement sframe handling
Date: Thu, 3 Jul 2025 20:36:28 -0400 [thread overview]
Message-ID: <20250703203628.09291030@batman.local.home> (raw)
In-Reply-To: <7eea50a5-e1b0-4319-9a25-cb8b327a836d@linux.ibm.com>
On Wed, 2 Jul 2025 14:57:22 +0200
Jens Remus <jremus@linux.ibm.com> wrote:
> Additionally it would make sense to include the patches from Josh that
> add SFrame information to the vDSO on x86 [3].
>
> [1]: [PATCH v12 00/11] perf: Support the deferred unwinding infrastructure,
> https://lore.kernel.org/linux-trace-kernel/20250701180410.755491417@goodmis.org/
>
> [2]: https://lore.kernel.org/linux-trace-kernel/51903e66-56bc-42a4-b80c-9c3223e2a48a@linux.ibm.com/
>
> [3]: [PATCH v6 0/6] x86/vdso: VDSO updates and fixes for sframes,
> https://lore.kernel.org/all/20250425023750.669174660@goodmis.org/
I didn't add the VDSO yet, but I just pushed to the linux-trace.git
tree as:
unwind/main
that has my latest perf and sframe code merged. It's my work in
progress and is not what I published yet as patches.
It's firework holiday here so I'm going to be mostly offline until Monday.
-- Steve
prev parent reply other threads:[~2025-07-04 0:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 18:49 [PATCH v7 00/12] unwind_deferred: Implement sframe handling Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 01/12] unwind_user/sframe: Add support for reading .sframe headers Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 02/12] unwind_user/sframe: Store sframe section data in per-mm maple tree Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 03/12] x86/uaccess: Add unsafe_copy_from_user() implementation Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 04/12] unwind_user/sframe: Add support for reading .sframe contents Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 05/12] unwind_user/sframe: Detect .sframe sections in executables Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 06/12] unwind_user/sframe: Wire up unwind_user to sframe Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 07/12] unwind_user/sframe/x86: Enable sframe unwinding on x86 Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 08/12] unwind_user/sframe: Remove .sframe section on detected corruption Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 09/12] unwind_user/sframe: Show file name in debug output Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 10/12] unwind_user/sframe: Enable debugging in uaccess regions Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 11/12] unwind_user/sframe: Add .sframe validation option Steven Rostedt
2025-07-01 18:49 ` [PATCH v7 12/12] [DO NOT APPLY] unwind_user/sframe: Add prctl() interface for registering .sframe sections Steven Rostedt
2025-07-02 12:57 ` [PATCH v7 00/12] unwind_deferred: Implement sframe handling Jens Remus
2025-07-02 16:47 ` Steven Rostedt
2025-07-04 0:36 ` Steven Rostedt [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=20250703203628.09291030@batman.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=axboe@kernel.dk \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--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=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=peterz@infradead.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