From: "H. Peter Anvin" <hpa@zytor.com>
To: Jens Remus <jremus@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org,
Steven Rostedt <rostedt@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.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>, Kees Cook <kees@kernel.org>,
"Carlos O'Donell" <codonell@redhat.com>,
Sam James <sam@gentoo.org>, Dylan Hatch <dylanbhatch@google.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH v6 0/6] x86/vdso: VDSO updates and fixes for sframes
Date: Sun, 01 Feb 2026 00:23:31 -0800 [thread overview]
Message-ID: <B1CDD538-668D-48E3-A937-740B7D6575FA@zytor.com> (raw)
In-Reply-To: <20260129112726.892340-1-jremus@linux.ibm.com>
On January 29, 2026 3:27:20 AM PST, Jens Remus <jremus@linux.ibm.com> wrote:
>This enables generation of SFrame V3 stack trace information for VDSO on
>x86-64. It's a continuation of Josh's and Steve's work:
>
> https://lore.kernel.org/all/cover.1737511963.git.jpoimboe@kernel.org/
> https://lore.kernel.org/all/20250422183439.895236512@goodmis.org/
>
>This series focuses only on the VDSO code. They are helpful fixes
>and updates that doesn't rely on sframes (although the last patch
>is sframe related).
>
>This series applies on top of the latest unwind user sframe series
>"[PATCH v13 00/18] unwind_deferred: Implement sframe handling":
>https://lore.kernel.org/all/20260127150554.2760964-1-jremus@linux.ibm.com/
>
>Like above series it depends on the upcoming binutils 2.46 release to
>be used to build executables and libraries such as VDSO with SFrame V3
>stack trace information (using the assembler option --gsframe-3).
>
>Changes in v6:
>- SFrame V3 support (SFrame V2 is not supported).
>- Prevent GNU_SFRAME program table entry to empty .sframe section.
>- Integrate v5 review feedback. (Josh)
>
>Regards,
>Jens
>
>
>Josh Poimboeuf (6):
> x86/vdso: Fix DWARF generation for getrandom()
> x86/asm: Avoid emitting DWARF CFI for non-VDSO
> x86/asm: Simplify VDSO DWARF generation
> x86/vdso: Use SYM_FUNC_{START,END} in __kernel_vsyscall()
> x86/vdso: Use CFI macros in __vdso_sgx_enter_enclave()
> x86/vdso: Enable sframe generation in VDSO
>
> arch/Kconfig | 7 +++
> arch/x86/entry/vdso/Makefile | 10 +++--
> arch/x86/entry/vdso/vdso-layout.lds.S | 9 +++-
> arch/x86/entry/vdso/vdso32/system_call.S | 10 +----
> arch/x86/entry/vdso/vgetrandom-chacha.S | 3 +-
> arch/x86/entry/vdso/vsgx.S | 19 +++------
> arch/x86/include/asm/dwarf2.h | 54 +++++++++++++++++-------
> arch/x86/include/asm/linkage.h | 33 ++++++++++++---
> arch/x86/include/asm/vdso.h | 1 -
> 9 files changed, 97 insertions(+), 49 deletions(-)
>
This patchset clashes *hard* with the changes already in tip:x86/entry.
next prev parent reply other threads:[~2026-02-01 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 11:27 Jens Remus
2026-01-29 11:27 ` [PATCH v6 1/6] x86/vdso: Fix DWARF generation for getrandom() Jens Remus
2026-01-29 11:27 ` [PATCH v6 2/6] x86/asm: Avoid emitting DWARF CFI for non-VDSO Jens Remus
2026-01-29 11:27 ` [PATCH v6 3/6] x86/asm: Simplify VDSO DWARF generation Jens Remus
2026-01-29 11:27 ` [PATCH v6 4/6] x86/vdso: Use SYM_FUNC_{START,END} in __kernel_vsyscall() Jens Remus
2026-01-29 11:27 ` [PATCH v6 5/6] x86/vdso: Use CFI macros in __vdso_sgx_enter_enclave() Jens Remus
2026-01-29 11:27 ` [PATCH v6 6/6] x86/vdso: Enable sframe generation in VDSO Jens Remus
2026-02-01 8:23 ` H. Peter Anvin [this message]
2026-02-03 17:22 ` [PATCH v6 0/6] x86/vdso: VDSO updates and fixes for sframes Jens Remus
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=B1CDD538-668D-48E3-A937-740B7D6575FA@zytor.com \
--to=hpa@zytor.com \
--cc=Liam.Howlett@oracle.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=codonell@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dylanbhatch@google.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-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@kernel.org \
--cc=rppt@kernel.org \
--cc=sam@gentoo.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--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