From: Sebastian Ott <seott@redhat.com>
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,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Subject: Re: [PATCH v9 1/3] KVM: selftests: arm64: Report set_id_reg reads of test registers as tests
Date: Wed, 4 Nov 2026 12:32:17 +0100 (CET) [thread overview]
Message-ID: <4df3cceb-0d07-d787-b5b6-0a28433116f3@redhat.com> (raw)
In-Reply-To: <20261103-kvm-arm64-set-id-regs-aarch64-v9-1-ab32bc79fa9c@kernel.org>
On Tue, 3 Nov 2026, Mark Brown wrote:
> Currently when we run guest code to validate that the values we wrote to
> the registers are seen by the guest we assert that these values match using
> a KVM selftests level assert, resulting in unclear diagnostics if the test
> fails. Replace this assert with reporting a kselftest test per register.
>
> In order to support getting the names of the registers we repaint the array
> of ID_ registers to store the names and open code the rest.
>
> Reviewed-by: Ben Horgan <ben.horgan@arm.com>
> Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> Signed-off-by: Mark Brown <broonie@kernel.org>
[...]
> @@ -684,11 +719,20 @@ static void test_guest_reg_read(struct kvm_vcpu *vcpu)
> REPORT_GUEST_ASSERT(uc);
> break;
> case UCALL_SYNC:
> - val = test_reg_vals[encoding_to_range_idx(uc.args[2])];
> - val = reset_mutable_bits(uc.args[2], val);
> + expected_val = test_reg_vals[encoding_to_range_idx(uc.args[2])];
> + expected_val = reset_mutable_bits(uc.args[2], expected_val);
>
> /* Make sure the written values are seen by guest */
> - TEST_ASSERT_EQ(val, reset_mutable_bits(uc.args[2], uc.args[3]));
> + reg_id = uc.args[2];
^
Minor nit: this could be moved above and be used in 3 more places.
> + guest_val = reset_mutable_bits(uc.args[2], uc.args[3]);
> +
> + match = expected_val == guest_val;
> + if (!match)
> + ksft_print_msg("%lx != %lx\n",
> + expected_val, guest_val);
> + ksft_test_result(match,
> + "%s value seen in guest\n",
> + get_reg_name(reg_id));
> break;
> case UCALL_DONE:
> done = true;
next prev parent reply other threads:[~2026-11-04 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 18:19 [PATCH v9 0/3] KVM: selftests: arm64: Improve diagnostics from set_id_regs Mark Brown
2026-11-03 18:19 ` [PATCH v9 1/3] KVM: selftests: arm64: Report set_id_reg reads of test registers as tests Mark Brown
2026-11-04 11:32 ` Sebastian Ott [this message]
2026-11-03 18:19 ` [PATCH v9 2/3] KVM: selftests: arm64: Report register reset tests individually Mark Brown
2026-11-03 18:19 ` [PATCH v9 3/3] KVM: selftests: arm64: Make set_id_regs bitfield validity checks non-fatal Mark Brown
2026-11-04 11:37 ` [PATCH v9 0/3] KVM: selftests: arm64: Improve diagnostics from set_id_regs Sebastian Ott
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=4df3cceb-0d07-d787-b5b6-0a28433116f3@redhat.com \
--to=seott@redhat.com \
--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=ljs@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 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®