From: Stephen Hemminger <stephen@networkplumber.org>
To: uk7b@foxmail.com
Cc: dev@dpdk.org, sunyuechi <sunyuechi@iscas.ac.cn>,
Stanislaw Kardach <stanislaw.kardach@gmail.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2 1/3] config/riscv: detect V extension
Date: Wed, 4 Jun 2025 12:54:59 -0700 [thread overview]
Message-ID: <20250604125459.6291fde2@hermes.local> (raw)
In-Reply-To: <tencent_530B1E13D57A8BD821C26287B971ACE9B007@qq.com>
On Wed, 4 Jun 2025 19:49:16 +0800
uk7b@foxmail.com wrote:
> From: sunyuechi <sunyuechi@iscas.ac.cn>
>
> This patch is derived from "config/riscv: detect presence of Zbc
> extension with modifications".
>
> The RISC-V C api defines architecture extension test macros
> These let us detect whether the V extension is supported on the
> compiler and -march we're building with. The C api also defines V
> intrinsics we can use rather than inline assembly on newer versions of
> GCC (14.1.0+) and Clang (18.1.0+).
>
> If the V extension and intrinsics are both present and we can detect
> the V extension at runtime, we define a flag, RTE_RISCV_FEATURE_V.
>
> Signed-off-by: sunyuechi <sunyuechi@iscas.ac.cn>
Need entry in .mailmap as first patch, we keep track of contributions.
Since Signed-off-by has legal meaning you need to use full legal name.
By giving Signed-off-by you are saying that "yes, I have full legal right
to open source this".
next prev parent reply other threads:[~2025-06-04 19:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 16:57 [PATCH 1/3] config/riscv: detect V extension uk7b
2025-06-04 11:49 ` [PATCH v2 0/3] Add RISC-V V extension detection and LPM optimization uk7b
2025-06-04 11:49 ` [PATCH v2 1/3] config/riscv: detect V extension uk7b
2025-06-04 19:54 ` Stephen Hemminger [this message]
2025-06-04 11:49 ` [PATCH v2 2/3] lib/lpm: R-V V rte_lpm_lookupx4 uk7b
2025-06-04 11:49 ` [PATCH v2 3/3] riscv: override machine_args only when default uk7b
2025-06-04 13:07 ` [PATCH v2 0/3] Add RISC-V V extension detection and LPM optimization uk7b
2025-06-04 13:16 ` 孙越池
2025-06-04 13:07 ` [PATCH v2 1/3] config/riscv: detect V extension uk7b
2025-06-04 13:07 ` [PATCH v2 2/3] lib/lpm: R-V V rte_lpm_lookupx4 uk7b
2025-06-04 13:07 ` [PATCH v2 3/3] riscv: override machine_args only when default uk7b
2025-06-04 15:47 ` [PATCH v3 0/3] Add RISC-V V extension detection and LPM optimization uk7b
[not found] ` <20250604154720.3078131-1-uk7b@foxmail.com>
2025-06-04 15:47 ` [PATCH v3 1/3] config/riscv: detect V extension uk7b
2025-06-04 15:47 ` [PATCH v3 2/3] lib/lpm: R-V V rte_lpm_lookupx4 uk7b
2025-06-04 15:47 ` [PATCH v3 3/3] riscv: override machine_args only when default uk7b
2025-06-05 10:58 ` [PATCH v4 0/3] [PATCH v4 0/3] Add RISC-V V extension detection and LPM optimization uk7b
2025-06-11 14:59 ` [PATCH v5 " uk7b
2025-06-27 3:58 ` [PATCH v6 " uk7b
[not found] ` <20250627035814.670775-1-uk7b@foxmail.com>
2025-06-27 3:58 ` [PATCH v6 1/3] config/riscv: detect V extension uk7b
2025-06-27 3:58 ` [PATCH v6 2/3] lib/lpm: R-V V rte_lpm_lookupx4 uk7b
2025-06-27 3:58 ` [PATCH v6 3/3] riscv: override machine_args only when default uk7b
[not found] ` <20250611145915.854026-1-uk7b@foxmail.com>
2025-06-11 14:59 ` [PATCH v5 1/3] config/riscv: detect V extension uk7b
2025-06-11 14:59 ` [PATCH v5 2/3] lib/lpm: R-V V rte_lpm_lookupx4 uk7b
2025-06-11 14:59 ` [PATCH v5 3/3] riscv: override machine_args only when default uk7b
2025-06-27 2:31 ` Stanisław Kardach
2025-06-27 4:03 ` 孙越池
[not found] ` <20250605105844.3931758-1-uk7b@foxmail.com>
2025-06-05 10:58 ` [PATCH v4 1/3] config/riscv: detect V extension uk7b
2025-06-05 10:58 ` [PATCH v4 2/3] lib/lpm: R-V V rte_lpm_lookupx4 uk7b
2025-06-11 11:52 ` Medvedkin, Vladimir
2025-06-11 15:04 ` 孙越池
2025-06-05 10:58 ` [PATCH v4 3/3] riscv: override machine_args only when default uk7b
-- strict thread matches above, loose matches on Subject: below --
2025-06-04 11:33 [PATCH v2 1/3] config/riscv: detect V extension uk7b
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=20250604125459.6291fde2@hermes.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stanislaw.kardach@gmail.com \
--cc=sunyuechi@iscas.ac.cn \
--cc=uk7b@foxmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.