From: Thomas Monjalon <thomas@monjalon.net>
To: sunyuechi@iscas.ac.cn, dangshiwei <1138222970gg@gmail.com>
Cc: dev@dpdk.org, stanislaw.kardach@gmail.com
Subject: Re: [PATCH v2] eal/riscv: add Z sub-extension detection via hwprobe syscall
Date: Mon, 01 Jun 2026 22:24:54 +0200 [thread overview]
Message-ID: <sNysWPxOScOg-GwsJvuWUQ@monjalon.net> (raw)
In-Reply-To: <20260323041714.4386-1-1138222970gg@gmail.com>
Hello,
We are waiting for a review of this patch.
The maintainer is Sun Yuechi.
23/03/2026 05:17, dangshiwei:
> The existing RISC-V rte_cpuflags implementation only detects
> single-letter ISA extensions (A, C, D, F, M, V, etc.) via
> AT_HWCAP. Z sub-extensions such as Zba, Zbb, Zbc, Zawrs and
> cryptography extensions (Zksed, Zksh, Zknd, Zkne) are not
> visible through AT_HWCAP and therefore cannot be used for
> runtime dispatch.
>
> Linux 6.4 introduced the riscv_hwprobe syscall (NR 258) which
> exposes Z sub-extensions via the RISCV_HWPROBE_KEY_IMA_EXT_0
> key as a 64-bit bitmask. This patch adds support for querying
> Z sub-extensions through this interface.
>
> Changes:
> - Add REG_HWPROBE_EXT0 source to cpu_register_t
> - Fix hwcap_registers_t type from uint32_t to uint64_t to
> avoid truncation of AT_HWCAP on 64-bit platforms
> - Call riscv_hwprobe at EAL init via RTE_INIT and cache the
> result; falls back silently on kernels older than 6.4
> - Add 56 new enum values for Z sub-extensions in rte_cpuflags.h
> - Extend cpuflags_autotest to cover all new flags
>
> Signed-off-by: dangshiwei <1138222970gg@gmail.com>
Please could you separate you first and family names?
Thank you
next prev parent reply other threads:[~2026-06-01 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 14:40 [PATCH] eal/riscv: add Z sub-extension detection via hwprobe syscall dangshiwei
2026-03-23 4:17 ` [PATCH v2] " dangshiwei
2026-06-01 20:24 ` Thomas Monjalon [this message]
2026-06-02 5:28 ` sunyuechi
-- strict thread matches above, loose matches on Subject: below --
2026-03-23 4:07 dangshiwei
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=sNysWPxOScOg-GwsJvuWUQ@monjalon.net \
--to=thomas@monjalon.net \
--cc=1138222970gg@gmail.com \
--cc=dev@dpdk.org \
--cc=stanislaw.kardach@gmail.com \
--cc=sunyuechi@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox