KVM: selftests: Start at iteration 0 instead of -1
authorDavid Matlack <dmatlack@google.com>
Thu, 11 Nov 2021 00:12:54 +0000 (00:12 +0000)
committerPaolo Bonzini <pbonzini@redhat.com>
Tue, 16 Nov 2021 12:43:27 +0000 (07:43 -0500)
commit36c5ad73d7016f34146cf0821c78f08737bdb5e9
tree628d9653bc322f2db33d3ff638a8f0bc0b159b86
parent13bbc70329c8df003e64c4fbea8678f9db0e75d5
KVM: selftests: Start at iteration 0 instead of -1

Start at iteration 0 instead of -1 to avoid having to initialize
vcpu_last_completed_iteration when setting up vCPU threads. This
simplifies the next commit where we move vCPU thread initialization
out to a common helper.

No functional change intended.

Signed-off-by: David Matlack <dmatlack@google.com>
Message-Id: <20211111001257.1446428-2-dmatlack@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
tools/testing/selftests/kvm/access_tracking_perf_test.c