The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: "Paul Walmsley" <pjw@kernel.org>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Albert Ou" <aou@eecs.berkeley.edu>,
	"Alexandre Ghiti" <alex@ghiti.fr>,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	"André Almeida" <andrealmeid@igalia.com>,
	"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
	"Thomas Gleixner" <tglx@kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>
Subject: Re: [PATCH v3 5/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock()
Date: Mon, 20 Jul 2026 13:37:59 +0200	[thread overview]
Message-ID: <87ldb5evs8.fsf@yellow.woof> (raw)
In-Reply-To: <20260717142423-c5be3c7c-d4cb-4a68-8e85-3e3754e42666@linutronix.de>

Thomas Weißschuh <thomas.weissschuh@linutronix.de> writes:
> Can it ever happen that the toolchain has differing zacas support between
> 32-bit and 64-bit? Then cpu_supports_zacas() may not be sufficient.

No idea. Probably not.

But if it does differ, we will get a clear compile-time error message
(unrecognized instruction or something like that). We can worry about it then.

> If it is guaranteed to be in sync I would prefer to reuse
> CONFIG_TOOLCHAIN_HAS_ZACAS instead of the cc-option check in the Makefile
> to make that clear and error out early if it should ever change.

I intend to apply Vivian's .option suggestion. That won't be required then.
>
> Also this assumes that compat vDSO alternative patching works.
> But this is not the case. My series [0] to implement it has not yet been
> applied. This revision is missing the note about this dependency.
>
> [0] https://lore.kernel.org/all/20260630-riscv-vdso32-alternative-v1-0-a32fd89b7b1c@linutronix.de/

Right, thanks.

> Could be :
>
> vdso-syms += __vdso_futex_robust_list$(BITS)_try_unlock

Wasn't aware that BITS exists, nice!

Nam

  reply	other threads:[~2026-07-20 11:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  8:06 [PATCH v3 0/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock() Nam Cao
2026-07-17  8:06 ` [PATCH v3 1/5] riscv: compat_vdso: switch to standard kbuild rule Nam Cao
2026-07-17 12:17   ` Thomas Weißschuh
2026-07-17  8:06 ` [PATCH v3 2/5] riscv: compat_vdso: Allow *.c source files Nam Cao
2026-07-17 12:19   ` Thomas Weißschuh
2026-07-17  8:06 ` [PATCH v3 3/5] riscv: compat_vdso: Introduce COMPAT_MARCH variable Nam Cao
2026-07-17 12:19   ` Thomas Weißschuh
2026-07-17  8:06 ` [PATCH v3 4/5] riscv: compat_vdso: Build with zacas if available Nam Cao
2026-07-17 12:23   ` Thomas Weißschuh
2026-07-17 12:38   ` Vivian Wang
2026-07-17 12:44     ` Vivian Wang
2026-07-20 11:17     ` Nam Cao
2026-07-17  8:06 ` [PATCH v3 5/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock() Nam Cao
2026-07-17 12:37   ` Thomas Weißschuh
2026-07-20 11:37     ` Nam Cao [this message]
2026-07-20 11:42       ` Thomas Weißschuh
2026-07-20 11:50         ` Nam Cao

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=87ldb5evs8.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --cc=alex@ghiti.fr \
    --cc=andrealmeid@igalia.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=palmer@dabbelt.com \
    --cc=peterz@infradead.org \
    --cc=pjw@kernel.org \
    --cc=tglx@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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