From: sashiko-bot@kernel.org
To: "Inochi Amaoto" <inochiama@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v5 8/8] KVM: riscv: selftests: add Zicfiss/Zicfilp extension to get-reg-list test
Date: Mon, 06 Jul 2026 02:39:34 +0000 [thread overview]
Message-ID: <20260706023935.81A001F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706022046.214956-9-inochiama@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `RISCV_CSR_ZICFISS` macro generates an uncompilable C code string when outputting registers.
--
commit ffbde58160b6dea5b92bb36fa48c6dca47305718
Author: Inochi Amaoto <inochiama@gmail.com>
KVM: riscv: selftests: add Zicfiss/Zicfilp extension to get-reg-list test
The KVM RISC-V allows Zicfiss/Zicfilp extensions for Guest/VM so this adds
these extensions to the get-reg-list test.
> diff --git a/tools/testing/selftests/kvm/riscv/get-reg-list.c b/tools/testing/selftests/kvm/riscv/get-reg-list.c
> index 94e33b2ee7963..49a4be8250315 100644
> --- a/tools/testing/selftests/kvm/riscv/get-reg-list.c
> +++ b/tools/testing/selftests/kvm/riscv/get-reg-list.c
[ ... ]
> @@ -358,6 +360,8 @@ static const char *core_id_to_str(const char *prefix, __u64 id)
> "KVM_REG_RISCV_CSR_AIA | KVM_REG_RISCV_CSR_REG(" #csr ")"
> #define RISCV_CSR_SMSTATEEN(csr) \
> "KVM_REG_RISCV_CSR_SMSTATEEN | KVM_REG_RISCV_CSR_REG(" #csr ")"
> +#define RISCV_CSR_ZICFISS(csr) \
> + "KVM_REG_RISCV_CSR_ZICFISS | KVM_REG_RISCV_CSR_REG(" #csr ")"
[Severity: Medium]
Does this macro generate an uncompilable C code string?
When outputting registers (such as when a test fails or when running with
--print-list), this macro will print KVM_REG_RISCV_CSR_REG(ssp) instead of
KVM_REG_RISCV_CSR_ZICFISS_REG(ssp).
Since ssp is in struct kvm_riscv_zicfiss_csr rather than struct
kvm_riscv_csr, copying and pasting this output to update expected register
lists will cause a build failure.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260706022046.214956-1-inochiama@gmail.com?part=8
prev parent reply other threads:[~2026-07-06 2:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 2:20 [PATCH v5 0/8] RISC-V: KVM: Add Svadu/Zicfiss/Zicfilp FWFT support Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` [PATCH v5 1/8] RISC-V: KVM: Add support for Svadu FWFT features Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:40 ` sashiko-bot
2026-07-07 2:46 ` Inochi Amaoto
2026-07-07 2:46 ` Inochi Amaoto
2026-07-07 2:46 ` Inochi Amaoto
2026-07-07 7:43 ` Anup Patel
2026-07-07 7:43 ` Anup Patel
2026-07-07 7:43 ` Anup Patel
2026-07-07 7:51 ` Inochi Amaoto
2026-07-07 7:51 ` Inochi Amaoto
2026-07-07 7:51 ` Inochi Amaoto
2026-07-06 2:20 ` [PATCH v5 2/8] KVM: riscv: selftests: add Svadu FWFT extension to get-reg-list test Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` [PATCH v5 3/8] RISC-V: KVM: Allow Zicfiss/Zicfilp extensions for Guest/VM Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` [PATCH v5 4/8] RISC-V: KVM: Add ssp context save/restore Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` [PATCH v5 5/8] RISC-V: KVM: Handle software-check exits for VCPU Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` [PATCH v5 6/8] RISC-V: KVM: Delegate SPELP bit to VS/VU mode if landing pad is enabled Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` [PATCH v5 7/8] RISC-V: KVM: Add support for control-flow integrity FWFT features Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:42 ` sashiko-bot
2026-07-06 2:20 ` [PATCH v5 8/8] KVM: riscv: selftests: add Zicfiss/Zicfilp extension to get-reg-list test Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:20 ` Inochi Amaoto
2026-07-06 2:39 ` sashiko-bot [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=20260706023935.81A001F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=inochiama@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.