diff options
author | Peter Xu <peterx@redhat.com> | 2020-09-30 21:22:28 -0400 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-11-08 06:03:11 -0500 |
commit | 3031e0288e60f09533339e61117b83099a6e126e (patch) | |
tree | 1ba4b3bb53beb51c39d31c8729cce9fdea595025 | |
parent | 31d212959179015bc07f3af4e890cadd26e01ee0 (diff) | |
download | linux-stable-3031e0288e60f09533339e61117b83099a6e126e.tar.gz linux-stable-3031e0288e60f09533339e61117b83099a6e126e.tar.bz2 linux-stable-3031e0288e60f09533339e61117b83099a6e126e.zip |
KVM: selftests: Always clear dirty bitmap after iteration
We used not to clear the dirty bitmap before because KVM_GET_DIRTY_LOG
would overwrite it the next time it copies the dirty log onto it.
In the upcoming dirty ring tests we'll start to fetch dirty pages from
a ring buffer, so no one is going to clear the dirty bitmap for us.
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20201001012228.5916-1-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
-rw-r--r-- | tools/testing/selftests/kvm/dirty_log_test.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/testing/selftests/kvm/dirty_log_test.c b/tools/testing/selftests/kvm/dirty_log_test.c index 752ec158ac59..6a8275a22861 100644 --- a/tools/testing/selftests/kvm/dirty_log_test.c +++ b/tools/testing/selftests/kvm/dirty_log_test.c @@ -195,7 +195,7 @@ static void vm_dirty_log_verify(enum vm_guest_mode mode, unsigned long *bmap) page); } - if (test_bit_le(page, bmap)) { + if (test_and_clear_bit_le(page, bmap)) { host_dirty_count++; /* * If the bit is set, the value written onto |