Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: Yao Zihong <zihong.plct@isrc.iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	 alexghiti@rivosinc.com, shuah@kernel.org,
	samuel.holland@sifive.com, evan@rivosinc.com,
	 cleger@rivosinc.com, zihongyao@outlook.com,
	zhangyin2018@iscas.ac.cn,  Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>
Subject: Re: [PATCH v2 0/4] riscv: hwprobe: Add Zicbop support
Date: Thu, 9 Oct 2025 12:09:57 -0500	[thread overview]
Message-ID: <20251009-440720dc2e40b8a0b8296956@orel> (raw)
In-Reply-To: <20251009134318.23040-1-zihong.plct@isrc.iscas.ac.cn>

On Thu, Oct 09, 2025 at 09:41:50PM +0800, Yao Zihong wrote:
> Changes since v1:
> ------------------
> - Bump RISCV_HWPROBE_MAX_KEY (modified 1/4).
> - Add documentation for the Zicbop hwprobe bit/key (new 3/4).
> - Add a selftest(prefetch.c) for Zicbop (new 4/4).
> 
> Add UAPI and kernel plumbing to expose the Zicbop extension presence
> and its block size through hwprobe. The interface mirrors
> Zicbom/Zicboz. This allows userspace to safely discover and optimize
> for Zicbop when available.
> 
> Background: Zicbop is mandated by the RVA22U64 profile. Downstream may
> combine the presence bit with ZICBOP_BLOCK_SIZE to make profile-level
> policy decisions or enable Zicbop-specific optimizations.
> 
> Yao Zihong (4):
>   uapi: riscv: hwprobe: Add Zicbop extension bit and block-size key
>   riscv: hwprobe: Report Zicbop presence and block size
>   docs: riscv: Document hwprobe for Zicbop
>   selftests/riscv: Add Zicbop prefetch test
> 
>  Documentation/arch/riscv/hwprobe.rst          |   8 +-
>  arch/riscv/include/asm/hwprobe.h              |   2 +-
>  arch/riscv/include/uapi/asm/hwprobe.h         |   2 +
>  arch/riscv/kernel/sys_hwprobe.c               |   6 +
>  .../testing/selftests/riscv/hwprobe/Makefile  |   5 +-
>  .../selftests/riscv/hwprobe/prefetch.c        | 236 ++++++++++++++++++
>  6 files changed, 256 insertions(+), 3 deletions(-)
>  create mode 100644 tools/testing/selftests/riscv/hwprobe/prefetch.c
> 
> -- 
> 2.47.2
>

I'm not sure why patches 1-3 aren't just squashed together like commit
eb1003970940 ("RISC-V: hwprobe: Expose Zicbom extension and its block
size") does for zicbom.

Thanks,
drew

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

  parent reply	other threads:[~2025-10-09 17:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 13:41 [PATCH v2 0/4] riscv: hwprobe: Add Zicbop support Yao Zihong
2025-10-09 13:41 ` [PATCH v2 1/4] uapi: riscv: hwprobe: Add Zicbop extension bit and block-size key Yao Zihong
2025-10-09 17:08   ` Andrew Jones
2025-10-09 13:41 ` [PATCH v2 2/4] riscv: hwprobe: Report Zicbop presence and block size Yao Zihong
2025-10-09 17:08   ` Andrew Jones
2025-10-09 13:41 ` [PATCH v2 3/4] docs: riscv: Document hwprobe for Zicbop Yao Zihong
2025-10-09 16:46   ` Andrew Jones
2025-10-09 13:41 ` [PATCH v2 4/4] selftests/riscv: Add Zicbop prefetch test Yao Zihong
2025-10-09 17:06   ` Andrew Jones
2025-10-13 16:16     ` Yao Zihong
2025-10-13 17:41       ` Andrew Jones
2025-10-09 17:09 ` Andrew Jones [this message]
2025-10-13 16:15   ` [PATCH v2 0/4] riscv: hwprobe: Add Zicbop support Yao Zihong

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=20251009-440720dc2e40b8a0b8296956@orel \
    --to=ajones@ventanamicro.com \
    --cc=alex@ghiti.fr \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=cleger@rivosinc.com \
    --cc=evan@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=shuah@kernel.org \
    --cc=zhangyin2018@iscas.ac.cn \
    --cc=zihong.plct@isrc.iscas.ac.cn \
    --cc=zihongyao@outlook.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