diff options
author | 2024-02-08 21:48:40 +0100 | |
---|---|---|
committer | 2024-02-28 20:58:12 +0000 | |
commit | 55f2cf88486cdc504176d4c5ebccdb65ea4be161 (patch) | |
tree | e17793525f99f4f8f48f19b37b7dfa0969ac200b /scripts/generate_rust_analyzer.py | |
parent | KVM: selftests: Move setting a vCPU's entry point to a dedicated API (diff) | |
download | linux-rng-55f2cf88486cdc504176d4c5ebccdb65ea4be161.tar.xz linux-rng-55f2cf88486cdc504176d4c5ebccdb65ea4be161.zip |
KVM: selftests: Add a macro to define a test with one vcpu
Most tests are currently not giving any proper output for the user
to see how much sub-tests have already been run, or whether new
sub-tests are part of a binary or not. So it would be good to
support TAP output in the KVM selftests. There is already a nice
framework for this in the kselftest_harness.h header which we can
use. But since we also need a vcpu in most KVM selftests, it also
makes sense to introduce our own wrapper around this which takes
care of creating a VM with one vcpu, so we don't have to repeat
this boilerplate in each and every test. Thus let's introduce
a KVM_ONE_VCPU_TEST() macro here which takes care of this.
Suggested-by: Sean Christopherson <seanjc@google.com>
Link: https://lore.kernel.org/all/Y2v+B3xxYKJSM%2FfH@google.com/
Signed-off-by: Thomas Huth <thuth@redhat.com>
Link: https://lore.kernel.org/r/20240208204844.119326-5-thuth@redhat.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions