From: patchwork-bot+linux-riscv@kernel.org
To: JinRui <jinrui@haiwei.tech>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, corbet@lwn.net,
skhan@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
alex@ghiti.fr, ajones@ventanamicro.com, cleger@rivosinc.com,
charlie@rivosinc.com, samuel.holland@sifive.com
Subject: Re: [PATCH] riscv: report Zfhmin/Zvfhmin when Zfh/Zvfh are present
Date: Tue, 01 Sep 2026 19:40:06 +0000 [thread overview]
Message-ID: <178829160640.1815744.5288519540181026085.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <7190E4DB338251C3+20260811081513.2849980-1-jinrui@haiwei.tech>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Paul Walmsley <pjw@kernel.org>:
On Tue, 11 Aug 2026 08:15:13 +0000 you wrote:
> The RISC-V ISA manual specifies that Zfh implies Zfhmin, a normative
> rule clarified in
> https://github.com/riscv/riscv-isa-manual/pull/3070. Zvfh likewise
> implies Zvfhmin, as stated by the vector extension specification.
>
> The kernel currently reports ZFH and ZFHMIN (and ZVFH and ZVFHMIN) as
> independent hwprobe bits derived only from what the device tree
> declares. Platforms that declare just "zfh" (Zfh being a superset that
> already contains all Zfhmin instructions) therefore report
> RISCV_HWPROBE_EXT_ZFHMIN=0, which breaks userspace RVA23 conformance
> checks (e.g. snapd installing core26 on riscv64).
>
> [...]
Here is the summary with links:
- riscv: report Zfhmin/Zvfhmin when Zfh/Zvfh are present
https://git.kernel.org/riscv/c/2dc1f8d0a5fd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-01 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 8:15 [PATCH] riscv: report Zfhmin/Zvfhmin when Zfh/Zvfh are present JinRui
2026-09-01 19:40 ` patchwork-bot+linux-riscv [this message]
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=178829160640.1815744.5288519540181026085.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=ajones@ventanamicro.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=corbet@lwn.net \
--cc=jinrui@haiwei.tech \
--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=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=samuel.holland@sifive.com \
--cc=skhan@linuxfoundation.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