From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Shuah Khan <shuah@kernel.org>, Oliver Upton <oupton@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>,
Peter Maydell <peter.maydell@linaro.org>,
Leonardo Bras <leo.bras@arm.com>,
Wei-Lin Chang <weilin.chang@arm.com>,
Yao Yuan <yaoyuan@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
kvmarm@lists.linux.dev, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v21 10/15] KVM: selftests: arm64: Check that invalid feature combinations are rejected
Date: Thu, 1 Oct 2026 17:35:42 +0100 [thread overview]
Message-ID: <ar6LVCUSUILd8K_d@gremlin> (raw)
In-Reply-To: <20260930-arm64-gcs-v21-10-3556644cd927@kernel.org>
On Wed, Sep 30, 2026 at 10:48:20PM +0100, Mark Brown wrote:
> In order to optimise fast paths KVM explicitly rejects configurations with
> S1PIE or S1POE but not TCR2, add coverage of this in the set_id_regs test.
> We have a list of invalid configurations, for each of them we try to run a
> VM and fail the test if it succeeds. We do feature detection by validating
> that we can write the fields with failing values.
>
> Since this misfiring can disrupt some of the other tests due to the kernel
> refusing to start guests we run the new tests first, improving diagnostics
> in the failing case.
Ah so this reflects the changes done to enforce the arch-valid s1pie/poe -> tcr
requirement it seems.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Everything seems sensible, so:
Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
> ---
> tools/testing/selftests/kvm/arm64/set_id_regs.c | 87 +++++++++++++++++++++++++
> 1 file changed, 87 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/arm64/set_id_regs.c b/tools/testing/selftests/kvm/arm64/set_id_regs.c
> index 7429a1055df5..cb5e6358c59c 100644
> --- a/tools/testing/selftests/kvm/arm64/set_id_regs.c
> +++ b/tools/testing/selftests/kvm/arm64/set_id_regs.c
> @@ -803,6 +803,89 @@ static void test_reset_preserves_id_regs(struct kvm_vcpu *vcpu)
> ksft_test_result_pass("%s\n", __func__);
> }
>
> +struct reg_ftr_val {
> + u64 reg;
> + u64 mask;
> + u64 val;
> +};
> +
> +#define REG_FTR_VAL(r, f, v) \
> + { .reg = ARM64_SYS_REG(sys_reg_Op0(SYS_ ## r), \
> + sys_reg_Op1(SYS_ ## r), \
> + sys_reg_CRn(SYS_ ## r), \
> + sys_reg_CRm(SYS_ ## r), \
> + sys_reg_Op2(SYS_ ## r)), \
> + .mask = r ## _ ## f ## _MASK, \
> + .val = (r ## _ ## f ## _ ## v << r ## _ ## f ## _SHIFT) }
> +
> +static const struct reg_ftr_val s1pie_no_tcr2[] = {
> + REG_FTR_VAL(ID_AA64MMFR3_EL1, TCRX, NI),
> + REG_FTR_VAL(ID_AA64MMFR3_EL1, S1PIE, IMP),
> + { }
> +};
> +
> +static const struct reg_ftr_val s1poe_no_tcr2[] = {
> + REG_FTR_VAL(ID_AA64MMFR3_EL1, TCRX, NI),
> + REG_FTR_VAL(ID_AA64MMFR3_EL1, S1POE, IMP),
> + { }
> +};
> +
> +struct ftr_config {
> + const char *name;
> + const struct reg_ftr_val *regs;
> +};
> +
> +static const struct ftr_config invalid_configs[] = {
> + { .name = "S1PIE without TCRX", .regs = s1pie_no_tcr2 },
> + { .name = "S1POE without TCRX", .regs = s1poe_no_tcr2 },
> +};
> +
> +static void test_invalid_config(const struct ftr_config *config)
> +{
> + struct kvm_vcpu *vcpu;
> + struct kvm_vm *vm;
> + const struct reg_ftr_val *field;
> + u64 val;
> + int ret;
> +
> + vm = vm_create(1);
> + vm_enable_cap(vm, KVM_CAP_ARM_WRITABLE_IMP_ID_REGS, 0);
> + vcpu = vm_vcpu_add(vm, 0, guest_code);
> + kvm_arch_vm_finalize_vcpus(vm);
> +
> + /*
> + * If we don't manage to set any of the fields assume the
> + * system does not support the feature and skip the test.
> + */
> + for (field = config->regs; field->reg; field++) {
> + val = vcpu_get_reg(vcpu, field->reg);
> + val &= ~field->mask;
> + val |= field->val;
> + __vcpu_set_reg(vcpu, field->reg, val);
> +
> + if (vcpu_get_reg(vcpu, field->reg) != val) {
> + ksft_print_msg("Test setup not supported\n");
> + ksft_test_result_skip("refuse %s\n", config->name);
> + goto out;
> + }
> + }
> +
> + ret = _vcpu_run(vcpu);
> + ksft_test_result(ret < 0 && errno == EINVAL, "refuse %s\n",
> + config->name);
> +out:
> + kvm_vm_free(vm);
> +}
> +
> +static void test_invalid_configs(void)
> +{
> + int i;
> +
> + for (i = 0; i < ARRAY_SIZE(invalid_configs); i++) {
> + test_invalid_config(&invalid_configs[i]);
> + }
VERY NITTY: This is insanely pedantic and I don't mind too much _really_
but in theory should be no {}'s :)
> +}
> +
> int main(void)
> {
> struct kvm_vcpu *vcpu;
> @@ -829,12 +912,16 @@ int main(void)
> ksft_print_header();
>
> test_cnt = 3 + MPAM_IDREG_TEST + MTE_IDREG_TEST;
> + test_cnt += ARRAY_SIZE(invalid_configs);
> for (i = 0; i < ARRAY_SIZE(test_regs); i++)
> for (j = 0; test_regs[i].ftr_bits[j].type != FTR_END; j++)
> test_cnt++;
>
> ksft_set_plan(test_cnt);
>
> + /* Do this first in case a break interferes with other tests */
> + test_invalid_configs();
> +
> test_vm_ftr_id_regs(vcpu, aarch64_only);
> test_vcpu_ftr_id_regs(vcpu);
> test_vcpu_non_ftr_id_regs(vcpu);
>
> --
> 2.47.3
>
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-01 16:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 21:48 [PATCH v21 00/15] KVM: arm64: Provide guest support for GCS Mark Brown
2026-09-30 21:48 ` [PATCH v21 01/15] arm64/gcs: Ensure FGTs for EL1 GCS instructions are disabled Mark Brown
2026-09-30 21:48 ` [PATCH v21 02/15] KVM: arm64: Refuse to start a guest with S1PIE or S1POE but not TCR2 Mark Brown
2026-10-01 10:50 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 03/15] KVM: arm64: Manage GCS access and registers for guests Mark Brown
2026-10-01 11:28 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 04/15] KVM: arm64: Ensure GCS memory effects are visible Mark Brown
2026-09-30 21:48 ` [PATCH v21 05/15] KVM: arm64: Set PSTATE.EXLOCK when entering an exception Mark Brown
2026-10-01 11:37 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 06/15] KVM: arm64: Validate GCS exception lock when emulating ERET Mark Brown
2026-10-01 13:10 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 07/15] KVM: arm64: Forward GCS exceptions to nested guests Mark Brown
2026-10-01 14:25 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 08/15] KVM: arm64: Enforce EXLOCK for SPSR and ELR Mark Brown
2026-10-01 16:26 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 09/15] KVM: arm64: Allow GCS to be enabled for guests Mark Brown
2026-10-01 16:29 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 10/15] KVM: selftests: arm64: Check that invalid feature combinations are rejected Mark Brown
2026-10-01 16:35 ` Lorenzo Stoakes (ARM) [this message]
2026-09-30 21:48 ` [PATCH v21 11/15] KVM: selftests: arm64: Add GCS registers to get-reg-list Mark Brown
2026-10-01 16:36 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 12/15] KVM: selftests: arm64: Add GCS to set_id_regs Mark Brown
2026-10-01 16:38 ` Lorenzo Stoakes (ARM)
2026-10-01 18:14 ` Mark Brown
2026-09-30 21:48 ` [PATCH v21 13/15] KVM: selftests: arm64: Only restore SPSR_EL1 and ELR_EL1 if they change Mark Brown
2026-10-01 16:41 ` Lorenzo Stoakes (ARM)
2026-09-30 21:48 ` [PATCH v21 14/15] tools: Synchronise the kernel esr.h Mark Brown
2026-10-01 16:47 ` Lorenzo Stoakes (ARM)
2026-10-01 17:27 ` Mark Brown
2026-09-30 21:48 ` [PATCH v21 15/15] KVM: selftests: arm64: Add GCS EXLOCK exception emulation test Mark Brown
2026-10-01 16:53 ` Lorenzo Stoakes (ARM)
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=ar6LVCUSUILd8K_d@gremlin \
--to=ljs@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=leo.bras@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@arm.com \
--cc=will@kernel.org \
--cc=yaoyuan@linux.alibaba.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®