KVM: selftests: Factor code out of demand_paging_test
authorBen Gardon <bgardon@google.com>
Tue, 27 Oct 2020 23:37:29 +0000 (16:37 -0700)
committerPaolo Bonzini <pbonzini@redhat.com>
Sun, 8 Nov 2020 11:03:34 +0000 (06:03 -0500)
commit4b5d12b0e21cc9f9f00201819844fcafb020ffad
treecb8c5ae356483ffecc0eb48104ded986799d6fe2
parentafdb1960071935cfd5c1908691a34cc6e36931f7
KVM: selftests: Factor code out of demand_paging_test

Much of the code in demand_paging_test can be reused by other, similar
multi-vCPU-memory-touching-perfromance-tests. Factor that common code
out for reuse.

No functional change expected.

This series was tested by running the following invocations on an Intel
Skylake machine:
dirty_log_perf_test -b 20m -i 100 -v 64
dirty_log_perf_test -b 20g -i 5 -v 4
dirty_log_perf_test -b 4g -i 5 -v 32
demand_paging_test -b 20m -v 64
demand_paging_test -b 20g -v 4
demand_paging_test -b 4g -v 32
All behaved as expected.

Signed-off-by: Ben Gardon <bgardon@google.com>
Message-Id: <20201027233733.1484855-2-bgardon@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
tools/testing/selftests/kvm/demand_paging_test.c
tools/testing/selftests/kvm/include/perf_test_util.h [new file with mode: 0644]