From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CCD543F6614 for ; Mon, 20 Jul 2026 11:38:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784547484; cv=none; b=t1ouo8FhyMxrKVOaX7T/6zGBfCbD1QCoYQORekCDg8h5utB+dC9OBLq7dya1sF5GQl4LdgxbhPDki+ubRWvpAgW+JQneUgclsui6E09l9TTKpTHZ6XV0p2sZc96t74s6Vi4MEXX+sq/tJsbS4FSQ0RfrOpGw1E7FkFvxel7Z2eg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784547484; c=relaxed/simple; bh=phFCsGFYgs1QpHy89Fcujz+dav1RJ/5A2UnSq6VyrOw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=JyT0SmOqTw0iCgl2MQ6upaEOpRJH8TtABmC5afW0j49MZ8LAjyzWayNX44+6ApzsneiUCjgy8R2t8Qj0ZcuDKaDeEJxuT44FcDkr1m+u1VN68u9Yao+FxGvZwU/rksxXKHbchbuaXfrswH/Uc+GBp/FSza+z6J4G7Mxkd/N3G9k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=Bfw094oq; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=fG8KDPZB; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="Bfw094oq"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="fG8KDPZB" From: Nam Cao DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1784547480; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=phFCsGFYgs1QpHy89Fcujz+dav1RJ/5A2UnSq6VyrOw=; b=Bfw094oq7+xt3FEeyBaZMoNqOFo32cwnFmyGeWmG5Bt2uAnZ7IFAF6xTz+f/849ZeyyfwE oXB570q/iLNMeIxW6UrZqSaoVV63RVzdzFtO6s/Nh3LZ7DBi3nmZdh+x03yO89Wi9IN28N p9p4QIE+bpZa3YdCjOjQh7OsJWEMLi2nQFnyqTODlNvQSWAaFN60zL670HO877AW69f/HR x62AtJofxvhd49aygvbFUsFCOZdHQRt5ykOk7gfjqQ9dsyetsiR1bS1CMBHNyOLyq6CW5l izYUJ3PvNFOBSeIpo6/LfeuBFkUbWmgqvW/wPPjwZng9MARnHx35Y1A0YtWwdA== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1784547480; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=phFCsGFYgs1QpHy89Fcujz+dav1RJ/5A2UnSq6VyrOw=; b=fG8KDPZBrq+f7GWWrnqAZeU4hIZHnXZjIr2v4w8j5J5P0FZZOre8cOpVYHyj9ul/isnK0E TIFvvoe30MQhJrBQ== To: Thomas =?utf-8?Q?Wei=C3=9Fschuh?= Cc: Paul Walmsley , Palmer Dabbelt , Albert Ou , Alexandre Ghiti , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, =?utf-8?Q?Andr=C3=A9?= Almeida , Mathieu Desnoyers , Thomas Gleixner , Peter Zijlstra , Sebastian Andrzej Siewior Subject: Re: [PATCH v3 5/5] riscv: vdso: Implement __vdso_futex_robust_try_unlock() In-Reply-To: <20260717142423-c5be3c7c-d4cb-4a68-8e85-3e3754e42666@linutronix.de> References: <20260717142423-c5be3c7c-d4cb-4a68-8e85-3e3754e42666@linutronix.de> Date: Mon, 20 Jul 2026 13:37:59 +0200 Message-ID: <87ldb5evs8.fsf@yellow.woof> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Thomas Wei=C3=9Fschuh 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 th= en. > 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-a3= 2fd89b7b1c@linutronix.de/ Right, thanks. > Could be : > > vdso-syms +=3D __vdso_futex_robust_list$(BITS)_try_unlock Wasn't aware that BITS exists, nice! Nam