kvm-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: patchwork-bot+linux-riscv@kernel.org
Cc: Xu Lu <luxu.kernel@bytedance.com>,
	linux-riscv@lists.infradead.org,  corbet@lwn.net,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	 aou@eecs.berkeley.edu, alex@ghiti.fr, robh@kernel.org,
	krzk+dt@kernel.org,  conor+dt@kernel.org, will@kernel.org,
	peterz@infradead.org,  boqun.feng@gmail.com,
	mark.rutland@arm.com, anup@brainfault.org,
	 atish.patra@linux.dev, pbonzini@redhat.com, shuah@kernel.org,
	 parri.andrea@gmail.com, ajones@ventanamicro.com,
	brs@rivosinc.com,  guoren@kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,  devicetree@vger.kernel.org,
	kvm@vger.kernel.org,  kvm-riscv@lists.infradead.org,
	linux-kselftest@vger.kernel.org,  apw@canonical.com,
	joe@perches.com, lukas.bulwahn@gmail.com
Subject: Re: [PATCH v4 00/10] riscv: Add Zalasr ISA extension support
Date: Wed, 19 Nov 2025 08:42:09 -0700 (MST)	[thread overview]
Message-ID: <b7dc669e-cc48-f163-0146-0ef37dbd19ec@kernel.org> (raw)
In-Reply-To: <176355541475.758643.7685467502830246491.git-patchwork-notify@kernel.org>

Folks,

On Wed, 19 Nov 2025, patchwork-bot+linux-riscv@kernel.org wrote:

> This series was applied to riscv/linux.git (for-next)
> by Paul Walmsley <pjw@kernel.org>:

This actually isn't true; I've only applied the first four patches (see 
below).

> On Mon, 20 Oct 2025 12:20:46 +0800 you wrote:
> > This patch adds support for the Zalasr ISA extension, which supplies the
> > real load acquire/store release instructions.
> > 
> > The specification can be found here:
> > https://github.com/riscv/riscv-zalasr/blob/main/chapter2.adoc
> > 
> > This patch seires has been tested with ltp on Qemu with Brensan's zalasr
> > support patch[1].
> > 
> > [...]
> 
> Here is the summary with links:
>   - [v4,01/10] riscv: Add ISA extension parsing for Zalasr
>     https://git.kernel.org/riscv/c/0597b9c8627e
>   - [v4,02/10] dt-bindings: riscv: Add Zalasr ISA extension description
>     https://git.kernel.org/riscv/c/6e2a0ff70abe
>   - [v4,03/10] riscv: hwprobe: Export Zalasr extension
>     https://git.kernel.org/riscv/c/d5e20628a882
>   - [v4,04/10] riscv: Introduce Zalasr instructions
>     https://git.kernel.org/riscv/c/c4139ea6717c
>   - [v4,05/10] riscv: Apply Zalasr to smp_load_acquire/smp_store_release
>     (no matching commit)
>   - [v4,06/10] riscv: Apply acquire/release semantics to arch_xchg/arch_cmpxchg operations
>     (no matching commit)
>   - [v4,07/10] riscv: Apply acquire/release semantics to arch_atomic operations
>     (no matching commit)
>   - [v4,08/10] riscv: Remove arch specific __atomic_acquire/release_fence
>     (no matching commit)
>   - [v4,09/10] RISC-V: KVM: Allow Zalasr extensions for Guest/VM
>     (no matching commit)
>   - [v4,10/10] RISC-V: KVM: selftests: Add Zalasr extensions to get-reg-list test
>     (no matching commit)

In terms of patches 5-8, we're still waiting for Xu Lu to update the 
patches based on Andrea's feedback.  Xu Lu, are you still planning to 
update these?


- Paul

-- 
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv

  reply	other threads:[~2025-11-19 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20  4:20 [PATCH v4 00/10] riscv: Add Zalasr ISA extension support Xu Lu
2025-10-20  4:20 ` [PATCH v4 01/10] riscv: Add ISA extension parsing for Zalasr Xu Lu
2025-10-20  4:20 ` [PATCH v4 02/10] dt-bindings: riscv: Add Zalasr ISA extension description Xu Lu
2025-10-20 17:21   ` Conor Dooley
2025-10-20  4:20 ` [PATCH v4 03/10] riscv: hwprobe: Export Zalasr extension Xu Lu
2025-10-20 13:46   ` Guo Ren
2025-10-20  4:20 ` [PATCH v4 04/10] riscv: Introduce Zalasr instructions Xu Lu
2025-10-20 13:34   ` Guo Ren
2025-10-20  4:34 ` [PATCH v4 00/10] riscv: Add Zalasr ISA extension support Xu Lu
2025-10-24 21:47 ` Andrea Parri
2025-11-19 12:30 ` patchwork-bot+linux-riscv
2025-11-19 15:42   ` Paul Walmsley [this message]
2025-11-19 15:57     ` 路旭

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=b7dc669e-cc48-f163-0146-0ef37dbd19ec@kernel.org \
    --to=pjw@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=apw@canonical.com \
    --cc=atish.patra@linux.dev \
    --cc=boqun.feng@gmail.com \
    --cc=brs@rivosinc.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=guoren@kernel.org \
    --cc=joe@perches.com \
    --cc=krzk+dt@kernel.org \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=luxu.kernel@bytedance.com \
    --cc=mark.rutland@arm.com \
    --cc=palmer@dabbelt.com \
    --cc=parri.andrea@gmail.com \
    --cc=patchwork-bot+linux-riscv@kernel.org \
    --cc=paul.walmsley@sifive.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=robh@kernel.org \
    --cc=shuah@kernel.org \
    --cc=will@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;
as well as URLs for NNTP newsgroup(s).