From: Szabolcs Nagy <nsz@port70.net>
To: Pincheng Wang <pincheng.plct@isrc.iscas.ac.cn>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH 1/1] riscv: add Zacas extension support for atomic CAS
Date: Tue, 21 Oct 2025 02:30:18 +0200 [thread overview]
Message-ID: <20251021003018.GC3520958@port70.net> (raw)
In-Reply-To: <20250918164720.337994-2-pincheng.plct@isrc.iscas.ac.cn>
* Pincheng Wang <pincheng.plct@isrc.iscas.ac.cn> [2025-09-19 00:47:20 +0800]:
> Add compile-time detection for RISC-V Zacas extension and use
> amocas.w.aqrl/amocas.d.aqrl instructions when available.
>
> When __riscv_zacas is defined, a_cas() and a_cas_p() use single amocas
> instructions instead of lr/sc loops. Falls back to existing lr/sc
> implementation when Zacas is not available.
is this a supported extension? are there users?
(implemented on existing cpus with released toolchain versions)
what cflags enable the extension? (how to test)
i can't review if the instructions have the right semantics,
but the code looks ok, with some comments below.
>
> Signed-off-by: Pincheng Wang <pincheng.plct@isrc.iscas.ac.cn>
> ---
> arch/riscv32/atomic_arch.h | 17 +++++++++++++++++
> arch/riscv64/atomic_arch.h | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 47 insertions(+)
>
> diff --git a/arch/riscv32/atomic_arch.h b/arch/riscv32/atomic_arch.h
> index 4d418f63..64ef05b7 100644
> --- a/arch/riscv32/atomic_arch.h
> +++ b/arch/riscv32/atomic_arch.h
> }
> +#ifdef __riscv_zacas
newline before #ifdef
> +#else /* Fallback to lr/sc when Zacas is not available */
...
> +#endif /* __riscv_zacas */
> \ No newline at end of file
newline after endif
i think ifdef comments are not needed in such a simple file.
> +++ b/arch/riscv64/atomic_arch.h
> @@ -4,6 +4,34 @@ static inline void a_barrier()
> __asm__ __volatile__ ("fence rw,rw" : : : "memory");
> }
>
> +#ifdef __riscv_zacas
> +
> +#define a_cas a_cas
> +static inline int a_cas(volatile int *p, int t, int s)
> +{
> + int old = t;
> + __asm__ __volatile__ (
> + "amocas.w.aqrl %0, %2, %1"
> + : "+r"(old), "+A"(*(volatile int *)p)
> + : "r"(s)
> + : "memory");
existing cas does not use +A constraint (check git log
why and ensure this is ok).
the ptr cast should not be needed. (same for rv32)
next prev parent reply other threads:[~2025-10-21 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 16:47 [musl] [PATCH 0/1] riscv: Add support for Zacas in atomic operations Pincheng Wang
2025-09-18 16:47 ` [musl] [PATCH 1/1] riscv: add Zacas extension support for atomic CAS Pincheng Wang
2025-10-21 0:30 ` Szabolcs Nagy [this message]
2025-10-21 3:05 ` Pincheng Wang
2025-10-16 15:37 ` [musl] [PATCH 0/1] riscv: Add support for Zacas in atomic operations Pincheng Wang
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=20251021003018.GC3520958@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
--cc=pincheng.plct@isrc.iscas.ac.cn \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).