Use KVM_SYNC_X86_VALID_FIELDS instead of open-coding the same three flags, ensuring the test stays in sync with any future additions.
Signed-off-by: Piotr Zarycki <[email protected]> --- tools/testing/selftests/kvm/x86/sync_regs_test.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/tools/testing/selftests/kvm/x86/sync_regs_test.c b/tools/testing/selftests/kvm/x86/sync_regs_test.c index e0c52321f87c..8f9239f9d357 100644 --- a/tools/testing/selftests/kvm/x86/sync_regs_test.c +++ b/tools/testing/selftests/kvm/x86/sync_regs_test.c @@ -79,7 +79,7 @@ static void compare_vcpu_events(struct kvm_vcpu_events *left, { } -#define TEST_SYNC_FIELDS (KVM_SYNC_X86_REGS|KVM_SYNC_X86_SREGS|KVM_SYNC_X86_EVENTS) +#define TEST_SYNC_FIELDS KVM_SYNC_X86_VALID_FIELDS #define INVALID_SYNC_FIELD 0x80000000 /* @@ -255,7 +255,6 @@ KVM_ONE_VCPU_TEST(sync_regs_test, req_and_verify_all_valid, guest_code) struct kvm_regs regs; /* Request and verify all valid register sets. */ - /* TODO: BUILD TIME CHECK: TEST_ASSERT(KVM_SYNC_X86_NUM_FIELDS != 3); */ run->kvm_valid_regs = TEST_SYNC_FIELDS; vcpu_run(vcpu); TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_IO); -- 2.54.0
