diff options
author | 2023-02-04 02:41:50 +0000 | |
---|---|---|
committer | 2023-03-14 10:20:08 -0400 | |
commit | e7062a98d0b3e0b42089f4c5da633a1ce41b807f (patch) | |
tree | 704e961a04421a4713bf23f73e74e479a9947a61 /scripts/generate_rust_analyzer.py | |
parent | KVM: selftests: Add helpers to make Xen-style VMCALL/VMMCALL hypercalls (diff) | |
download | linux-rng-e7062a98d0b3e0b42089f4c5da633a1ce41b807f.tar.xz linux-rng-e7062a98d0b3e0b42089f4c5da633a1ce41b807f.zip |
KVM: selftests: Use enum for test numbers in xen_shinfo_test
The xen_shinfo_test started off with very few iterations, and the numbers
we used in GUEST_SYNC() were precisely mapped to the RUNSTATE_xxx values
anyway to start with.
It has since grown quite a few more tests, and it's kind of awful to be
handling them all as bare numbers. Especially when I want to add a new
test in the middle. Define an enum for the test stages, and use it both
in the guest code and the host switch statement.
No functional change, if I can count to 24.
Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20230204024151.1373296-4-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions