From: "André Almeida" <andrealmeid@igalia.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Thomas Gleixner <tglx@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Nam Cao <namcao@linutronix.de>, Andy Lutomirski <luto@kernel.org>,
x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Nathan Chancellor <nathan@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Borislav Petkov <bp@alien8.de>, Nicolas Schier <nsc@kernel.org>,
kernel-dev@igalia.com
Subject: Re: [PATCH] vDSO, kbuild: Provide vDSO debug variants at runtime
Date: Wed, 15 Jul 2026 09:29:35 -0300 [thread overview]
Message-ID: <e49be8bf-a3f8-4b2f-8e2b-379f4885b194@igalia.com> (raw)
In-Reply-To: <17d3c3f6-f040-45b9-adf7-6ef1d7cf4e3e@igalia.com>
Em 08/07/2026 12:28, André Almeida escreveu:
> Em 08/07/2026 10:56, Thomas Weißschuh escreveu:
>> Finding the debug version of the vDSO is not trivial as there is no
>> common
>> scheme where it is placed. That's especially problematic for CI testing.
>>
>> The vDSO futex unlock mechanism requires for testing to have access to
>> the
>> inner labels of the unlock assembly, which are only accessible via the
>> debug so.
>>
>> Also for general debugging purposes it's convenient to have access to the
>> debug vDSO at a well defined place.
>>
>> The files are placed in /sys/kernel/vdso_debug.tar.xz. They use the
>> regular 'make vdso_install' layout, including build-id symlinks to find
>> the correct file for each process.
>>
>> The design is kept close to the ones of the similar IKCONFIG and
>> IKHEADERS.
>>
>> On x86 the x32 vDSO is derived from the x86_64 one, necessitating an
>> explicit dependency to avoid errors due to concurrent builds.
>>
>> Suggested-by: Thomas Gleixner <tglx@kernel.org>
>> Link: https://lore.kernel.org/lkml/20260602090536.045586688@kernel.org/
>> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
>> ---
>
> Thanks for your patch! Tested in arm64 (qemu) and it worked fine. I was
> just expecting that the file would be called "vdso.so.dbg", not "vdso.so".
>
> Tested-by: André Almeida <andrealmeid@igalia.com>
Also, how do you suggest to integrate this with kselftests? Maybe adding
an untar command to futex/functional/run.sh?
next prev parent reply other threads:[~2026-07-15 12:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 13:56 Thomas Weißschuh
2026-07-08 15:28 ` André Almeida
2026-07-15 12:29 ` André Almeida [this message]
2026-07-24 14:14 ` Thomas Weißschuh
2026-07-09 9:57 ` Vincenzo Frascino
2026-07-09 19:06 ` H. Peter Anvin
2026-07-10 6:36 ` Thomas Weißschuh
2026-07-10 7:32 ` H. Peter Anvin
2026-07-10 7:41 ` Thomas Weißschuh
2026-07-10 18:34 ` H. Peter Anvin
2026-07-13 13:17 ` Thomas Weißschuh
2026-10-27 20:22 ` Nicolas Schier
2026-10-28 0:02 ` H. Peter Anvin
2026-10-28 5:55 ` Thomas Weißschuh
2026-10-28 6:12 ` H. Peter Anvin
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=e49be8bf-a3f8-4b2f-8e2b-379f4885b194@igalia.com \
--to=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=namcao@linutronix.de \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--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
all inboxes | Powered by JetHome®