From: Thomas Gleixner <tglx@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Andrè Almeida" <andrealmeid@igalia.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Carlos O'Donell" <carlos@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Florian Weimer" <fweimer@redhat.com>,
"Rich Felker" <dalias@aerifal.cx>,
"Torvald Riegel" <triegel@redhat.com>,
"Darren Hart" <dvhart@infradead.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
"Uros Bizjak" <ubizjak@gmail.com>
Subject: Re: [patch V4 12/14] x86/vdso: Implement __vdso_futex_robust_try_unlock()
Date: Thu, 07 May 2026 11:29:01 +0200 [thread overview]
Message-ID: <878q9vwote.ffs@tglx> (raw)
In-Reply-To: <eb0fde3f-2609-4746-952e-032389472e1d@t-8ch.de>
On Wed, Apr 29 2026 at 10:44, Thomas Weißschuh wrote:
> On 2026-04-02 17:22:00+0200, Thomas Gleixner wrote:
> (...)
>
>> + * When CONFIG_COMPAT is enabled then the 64-bit VDSO provides two functions.
>> + * One for the regular 64-bit sized pending operation pointer and one for a
>> + * 32-bit sized pointer to support gaming emulators.
>
> These gaming emulators can emulate 32-bit code on 64-bit kernels even
> without CONFIG_COMPAT. At least this is how I understand Wine WoW64 and
> FEX-Emu. And in that case the 32-bit sized pointer function should be
> available unconditionally, without the dependency on CONFIG_COMPAT.
That might well be, but that requires also the ability to register a
32-bit robust list for a 64-bit process, which is not supported right
now.
So no, we are not exposing something half functional just because. That
needs to be mopped up once we add the multi-robust list stuff.
Thanks,
tglx
next parent reply other threads:[~2026-05-07 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260402151131.876492985@kernel.org>
[not found] ` <20260402151940.418303527@kernel.org>
[not found] ` <eb0fde3f-2609-4746-952e-032389472e1d@t-8ch.de>
2026-05-07 9:29 ` Thomas Gleixner [this message]
2026-05-07 9:48 ` [patch V4 12/14] x86/vdso: Implement __vdso_futex_robust_try_unlock() Thomas Weißschuh
2026-05-07 16:51 ` Thomas Gleixner
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=878q9vwote.ffs@tglx \
--to=tglx@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=andrealmeid@igalia.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=carlos@redhat.com \
--cc=dalias@aerifal.cx \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=triegel@redhat.com \
--cc=ubizjak@gmail.com \
/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