test_vm_ftr_id_regs() uses a simplified check for 32 bit ID registers since
it knows it will only run on ID registers. For clarity update this to use
the newly added is_aarch32_id_reg(), there should be no functional change.

Signed-off-by: Mark Brown <[email protected]>
---
 tools/testing/selftests/kvm/arm64/set_id_regs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/kvm/arm64/set_id_regs.c 
b/tools/testing/selftests/kvm/arm64/set_id_regs.c
index 908b3c8947d9..f703c6cfe132 100644
--- a/tools/testing/selftests/kvm/arm64/set_id_regs.c
+++ b/tools/testing/selftests/kvm/arm64/set_id_regs.c
@@ -503,7 +503,7 @@ 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) {
+                       if (aarch64_only && is_aarch32_id_reg(reg_id)) {
                                ksft_print_msg("%s on AARCH64 only system\n",
                                               ftr_bits[j].name);
                                ksft_test_result_skip("%s invalid write 
rejected\n",

-- 
2.47.3


Reply via email to