From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>, Oliver Upton <oupton@kernel.org>,
Ben Horgan <ben.horgan@arm.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 3/3] KVM: selftests: arm64: Make set_id_regs bitfield validatity checks non-fatal
Date: Mon, 28 Sep 2026 16:43:06 +0100 [thread overview]
Message-ID: <arqIqSd33vvr1_lC@gremlin> (raw)
In-Reply-To: <20260901-kvm-arm64-set-id-regs-aarch64-v7-3-7b065b0bda9a@kernel.org>
Typo in subject: validatity -> validity
On Tue, Sep 01, 2026 at 07:50:03PM +0100, Mark Brown wrote:
> Currently when set_id_regs encounters a problem checking validation of
> writes to feature registers it uses an immediately fatal assert to report
> the problem. This is not idiomatic for kselftest, and it is also not great
> for usability. The affected bitfield is not clearly reported and further
> tests do not have their results reported.
>
> Switch to using standard kselftest result reporting for the two asserts
> we do, these are non-fatal asserts so allow the program to continue and the
> test names include the affected field.
>
> Reviewed-by: Ben Horgan <ben.horgan@arm.com>
> Signed-off-by: Mark Brown <broonie@kernel.org>
One NIT below and typo noted above, with those addressed LGTM so:
Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---
> tools/testing/selftests/kvm/arm64/set_id_regs.c | 22 ++++++++++++++++------
> 1 file changed, 16 insertions(+), 6 deletions(-)
>
> diff --git a/tools/testing/selftests/kvm/arm64/set_id_regs.c b/tools/testing/selftests/kvm/arm64/set_id_regs.c
> index 3aa8886e8b70..385e1f1c0133 100644
> --- a/tools/testing/selftests/kvm/arm64/set_id_regs.c
> +++ b/tools/testing/selftests/kvm/arm64/set_id_regs.c
> @@ -422,6 +422,7 @@ static u64 test_reg_set_success(struct kvm_vcpu *vcpu, u64 reg,
> u8 shift = ftr_bits->shift;
> u64 mask = ftr_bits->mask;
> u64 val, new_val, ftr;
> + bool match;
>
> val = vcpu_get_reg(vcpu, reg);
> ftr = (val & mask) >> shift;
> @@ -434,7 +435,10 @@ static u64 test_reg_set_success(struct kvm_vcpu *vcpu, u64 reg,
>
> vcpu_set_reg(vcpu, reg, val);
> new_val = vcpu_get_reg(vcpu, reg);
> - TEST_ASSERT_EQ(new_val, val);
> + match = new_val == val;
> + if (!match)
> + ksft_print_msg("%lx != %lx\n", new_val, val);
> + ksft_test_result(match, "%s valid write succeeded\n", ftr_bits->name);
Same pattern (I wonder, not for this series, but perhaps a follow up whether
this could be generalised?)
>
> return new_val;
> }
> @@ -446,6 +450,7 @@ static void test_reg_set_fail(struct kvm_vcpu *vcpu, u64 reg,
> u64 mask = ftr_bits->mask;
> u64 val, old_val, ftr;
> int r;
> + bool match;
>
> val = vcpu_get_reg(vcpu, reg);
> ftr = (val & mask) >> shift;
> @@ -462,7 +467,10 @@ static void test_reg_set_fail(struct kvm_vcpu *vcpu, u64 reg,
> "Unexpected KVM_SET_ONE_REG error: r=%d, errno=%d", r, errno);
>
NIT:
There's a:
TEST_ASSERT(r < 0 && errno == EINVAL,
"Unexpected KVM_SET_ONE_REG error: r=%d, errno=%d", r, errno);
Above, do we want to make that non-fatal too?
> val = vcpu_get_reg(vcpu, reg);
> - TEST_ASSERT_EQ(val, old_val);
> + match = val == old_val;
> + if (!match)
> + ksft_print_msg("%lx != %lx\n", val, old_val);
> + ksft_test_result(match, "%s invalid write rejected\n", ftr_bits->name);
> }
>
> static u64 test_reg_vals[KVM_ARM_FEATURE_ID_RANGE_SIZE];
> @@ -502,7 +510,11 @@ static void test_vm_ftr_id_regs(struct kvm_vcpu *vcpu, bool aarch64_only)
> for (int j = 0; ftr_bits[j].type != FTR_END; j++) {
> /* Skip aarch32 reg on aarch64 only system, since they are RAZ/WI. */
> if (aarch64_only && sys_reg_CRm(reg_id) < 4) {
> - ksft_test_result_skip("%s on AARCH64 only system\n",
> + ksft_print_msg("%s on AARCH64 only system\n",
> + ftr_bits[j].name);
> + ksft_test_result_skip("%s invalid write rejected\n",
> + ftr_bits[j].name);
> + ksft_test_result_skip("%s valid write succeeded\n",
> ftr_bits[j].name);
> continue;
> }
> @@ -514,8 +526,6 @@ static void test_vm_ftr_id_regs(struct kvm_vcpu *vcpu, bool aarch64_only)
>
> test_reg_vals[idx] = test_reg_set_success(vcpu, reg,
> &ftr_bits[j]);
> -
> - ksft_test_result_pass("%s\n", ftr_bits[j].name);
> }
> }
> }
> @@ -882,7 +892,7 @@ int main(void)
> ID_REG_RESET_UNCHANGED_TEST;
> for (i = 0; i < ARRAY_SIZE(test_regs); i++)
> for (j = 0; test_regs[i].ftr_bits[j].type != FTR_END; j++)
> - test_cnt++;
> + test_cnt += 2;
>
> ksft_set_plan(test_cnt);
>
>
> --
> 2.47.3
>
>
--
Cheers, Lorenzo
prev parent reply other threads:[~2026-09-28 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 18:50 [PATCH v7 0/3] KVM: selftests: arm64: Improve diagnostics from set_id_regs Mark Brown
2026-09-01 18:50 ` [PATCH v7 1/3] KVM: selftests: arm64: Report set_id_reg reads of test registers as tests Mark Brown
2026-09-28 15:26 ` Lorenzo Stoakes (ARM)
2026-09-28 16:29 ` Mark Brown
2026-09-01 18:50 ` [PATCH v7 2/3] KVM: selftests: arm64: Report register reset tests individually Mark Brown
2026-09-28 15:32 ` Lorenzo Stoakes (ARM)
2026-09-01 18:50 ` [PATCH v7 3/3] KVM: selftests: arm64: Make set_id_regs bitfield validatity checks non-fatal Mark Brown
2026-09-28 15:43 ` Lorenzo Stoakes (ARM) [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=arqIqSd33vvr1_lC@gremlin \
--to=ljs@kernel.org \
--cc=ben.horgan@arm.com \
--cc=broonie@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.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.