From: Alexandre Ghiti <alex@ghiti.fr>
To: Chunyan Zhang <zhangchunyan@iscas.ac.cn>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Charlie Jenkins <charlie@rivosinc.com>,
Song Liu <song@kernel.org>, Yu Kuai <yukuai3@huawei.com>
Cc: linux-riscv@lists.infradead.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.lyra@gmail.com>
Subject: Re: [PATCH V3 5/5] raid6: test: Add support for RISC-V
Date: Fri, 18 Jul 2025 16:08:58 +0200 [thread overview]
Message-ID: <00a97b26-0269-4c07-99b9-33bb759067f5@ghiti.fr> (raw)
In-Reply-To: <20250718072711.3865118-6-zhangchunyan@iscas.ac.cn>
Hi Chunyan,
On 7/18/25 09:27, Chunyan Zhang wrote:
> From: Chunyan Zhang <zhang.lyra@gmail.com>
>
> Add RISC-V code to be compiled to allow the userspace raid6test program
> to be built and run on RISC-V.
>
> Signed-off-by: Chunyan Zhang <zhang.lyra@gmail.com>
> ---
> lib/raid6/test/Makefile | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/lib/raid6/test/Makefile b/lib/raid6/test/Makefile
> index 8f2dd2210ba8..09bbe2b14cce 100644
> --- a/lib/raid6/test/Makefile
> +++ b/lib/raid6/test/Makefile
> @@ -35,6 +35,11 @@ ifeq ($(ARCH),aarch64)
> HAS_NEON = yes
> endif
>
> +ifeq ($(findstring riscv,$(ARCH)),riscv)
> + CFLAGS += -I../../../arch/riscv/include -DCONFIG_RISCV=1
> + HAS_RVV = yes
> +endif
> +
> ifeq ($(findstring ppc,$(ARCH)),ppc)
> CFLAGS += -I../../../arch/powerpc/include
> HAS_ALTIVEC := $(shell printf '$(pound)include <altivec.h>\nvector int a;\n' |\
> @@ -63,6 +68,9 @@ else ifeq ($(HAS_ALTIVEC),yes)
> vpermxor1.o vpermxor2.o vpermxor4.o vpermxor8.o
> else ifeq ($(ARCH),loongarch64)
> OBJS += loongarch_simd.o recov_loongarch_simd.o
> +else ifeq ($(HAS_RVV),yes)
> + OBJS += rvv.o recov_rvv.o
> + CFLAGS += -DCONFIG_RISCV_ISA_V=1
> endif
>
> .c.o:
Reviewed-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Tested-by: Alexandre Ghiti <alexghiti@rivosinc.com>
Thanks for the new version, I'll take that for 6.17,
Alex
next prev parent reply other threads:[~2025-07-18 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 7:27 [PATCH V3 0/5] Add an optimization also raid6test for RISC-V support Chunyan Zhang
2025-07-18 7:27 ` [PATCH V3 1/5] raid6: riscv: Clean up unused header file inclusion Chunyan Zhang
2025-07-18 7:27 ` [PATCH V3 2/5] raid6: riscv: replace one load with a move to speed up the caculation Chunyan Zhang
2025-07-18 7:27 ` [PATCH V3 3/5] raid6: riscv: Prevent compiler with vector support to build already vectorized code Chunyan Zhang
2025-11-25 9:26 ` Paul Walmsley
2025-11-25 9:43 ` Chunyan Zhang
2025-07-18 7:27 ` [PATCH V3 4/5] raid6: riscv: Allow code to be compiled in userspace Chunyan Zhang
2025-07-18 7:27 ` [PATCH V3 5/5] raid6: test: Add support for RISC-V Chunyan Zhang
2025-07-18 14:08 ` Alexandre Ghiti [this message]
2025-10-13 1:42 ` Chunyan Zhang
2025-11-25 9:29 ` Paul Walmsley
2025-08-06 17:15 ` [PATCH V3 0/5] Add an optimization also raid6test for RISC-V support patchwork-bot+linux-riscv
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=00a97b26-0269-4c07-99b9-33bb759067f5@ghiti.fr \
--to=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=charlie@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=song@kernel.org \
--cc=yukuai3@huawei.com \
--cc=zhang.lyra@gmail.com \
--cc=zhangchunyan@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
all inboxes | Powered by JetHome®