From: Peter Xu <peterx@redhat.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: peterx@redhat.com,
Sean Christopherson <sean.j.christopherson@intel.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Andrew Jones <drjones@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH v11 07/13] KVM: selftests: Always clear dirty bitmap after iteration
Date: Wed, 8 Jul 2020 15:34:02 -0400 [thread overview]
Message-ID: <20200708193408.242909-8-peterx@redhat.com> (raw)
In-Reply-To: <20200708193408.242909-1-peterx@redhat.com>
We don't clear the dirty bitmap before because KVM_GET_DIRTY_LOG will
clear it for us before copying the dirty log onto it. However we'd
still better to clear it explicitly instead of assuming the kernel
will always do it for us.
More importantly, 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>
---
tools/testing/selftests/kvm/dirty_log_test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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
--
2.26.2
next prev parent reply other threads:[~2020-07-08 19:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 19:33 [PATCH v11 00/13] KVM: Dirty ring interface Peter Xu
2020-07-08 19:33 ` [PATCH v11 01/13] KVM: Cache as_id in kvm_memory_slot Peter Xu
2020-07-23 0:27 ` Sean Christopherson
2020-07-08 19:33 ` [PATCH v11 02/13] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR] Peter Xu
2020-07-23 0:29 ` Sean Christopherson
2020-07-08 19:33 ` [PATCH v11 03/13] KVM: Pass in kvm pointer into mark_page_dirty_in_slot() Peter Xu
2020-07-08 19:33 ` [PATCH v11 04/13] KVM: X86: Implement ring-based dirty memory tracking Peter Xu
2020-07-08 19:34 ` [PATCH v11 05/13] KVM: Make dirty ring exclusive to dirty bitmap log Peter Xu
2020-07-08 19:34 ` [PATCH v11 06/13] KVM: Don't allocate dirty bitmap if dirty ring is enabled Peter Xu
2020-07-08 19:34 ` Peter Xu [this message]
2020-07-08 19:34 ` [PATCH v11 08/13] KVM: selftests: Sync uapi/linux/kvm.h to tools/ Peter Xu
2020-07-08 19:34 ` [PATCH v11 09/13] KVM: selftests: Use a single binary for dirty/clear log test Peter Xu
2020-07-08 19:34 ` [PATCH v11 10/13] KVM: selftests: Introduce after_vcpu_run hook for dirty " Peter Xu
2020-07-08 19:34 ` [PATCH v11 11/13] KVM: selftests: Add dirty ring buffer test Peter Xu
2020-07-08 19:34 ` [PATCH v11 12/13] KVM: selftests: Let dirty_log_test async for dirty ring test Peter Xu
2020-07-08 19:34 ` [PATCH v11 13/13] KVM: selftests: Add "-c" parameter to dirty log test Peter Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200708193408.242909-8-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).