From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Hyman <huangy81@chinatelecom.cn>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
peterx@redhat.com
Subject: [PATCH v4 06/13] KVM: Create the KVMSlot dirty bitmap on flag changes
Date: Fri, 8 Jan 2021 11:50:43 -0500 [thread overview]
Message-ID: <20210108165050.406906-3-peterx@redhat.com> (raw)
In-Reply-To: <20210108165050.406906-1-peterx@redhat.com>
Previously we have two places that will create the per KVMSlot dirty
bitmap:
1. When a newly created KVMSlot has dirty logging enabled,
2. When the first log_sync() happens for a memory slot.
The 2nd case is lazy-init, while the 1st case is not (which is a fix
of what the 2nd case missed).
To do explicit initialization of dirty bitmaps, what we're missing is
to create the dirty bitmap when the slot changed from not-dirty-track
to dirty-track. Do that in kvm_slot_update_flags().
With that, we can safely remove the 2nd lazy-init.
This change will be needed for kvm dirty ring because kvm dirty ring
does not use the log_sync() interface at all.
Also move all the pre-checks into kvm_slot_init_dirty_bitmap().
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
---
accel/kvm/kvm-all.c | 23 +++++++++--------------
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
index d891a22a3b..445ce1b177 100644
--- a/accel/kvm/kvm-all.c
+++ b/accel/kvm/kvm-all.c
@@ -181,6 +181,8 @@ static QemuMutex kml_slots_lock;
#define kvm_slots_lock() qemu_mutex_lock(&kml_slots_lock)
#define kvm_slots_unlock() qemu_mutex_unlock(&kml_slots_lock)
+static void kvm_slot_init_dirty_bitmap(KVMSlot *mem);
+
static inline void kvm_resample_fd_remove(int gsi)
{
KVMResampleFd *rfd;
@@ -524,6 +526,7 @@ static int kvm_slot_update_flags(KVMMemoryListener *kml, KVMSlot *mem,
return 0;
}
+ kvm_slot_init_dirty_bitmap(mem);
return kvm_set_user_memory_region(kml, mem, false);
}
@@ -608,8 +611,12 @@ static int kvm_get_dirty_pages_log_range(MemoryRegionSection *section,
#define ALIGN(x, y) (((x)+(y)-1) & ~((y)-1))
/* Allocate the dirty bitmap for a slot */
-static void kvm_memslot_init_dirty_bitmap(KVMSlot *mem)
+static void kvm_slot_init_dirty_bitmap(KVMSlot *mem)
{
+ if (!(mem->flags & KVM_MEM_LOG_DIRTY_PAGES) || mem->dirty_bmap) {
+ return;
+ }
+
/*
* XXX bad kernel interface alert
* For dirty bitmap, kernel allocates array of size aligned to
@@ -660,11 +667,6 @@ static int kvm_physical_sync_dirty_bitmap(KVMMemoryListener *kml,
goto out;
}
- if (!mem->dirty_bmap) {
- /* Allocate on the first log_sync, once and for all */
- kvm_memslot_init_dirty_bitmap(mem);
- }
-
d.dirty_bitmap = mem->dirty_bmap;
d.slot = mem->slot | (kml->as_id << 16);
if (kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d) == -1) {
@@ -1197,14 +1199,7 @@ static void kvm_set_phys_mem(KVMMemoryListener *kml,
mem->start_addr = start_addr;
mem->ram = ram;
mem->flags = kvm_mem_flags(mr);
-
- if (mem->flags & KVM_MEM_LOG_DIRTY_PAGES) {
- /*
- * Reallocate the bmap; it means it doesn't disappear in
- * middle of a migrate.
- */
- kvm_memslot_init_dirty_bitmap(mem);
- }
+ kvm_slot_init_dirty_bitmap(mem);
err = kvm_set_user_memory_region(kml, mem, true);
if (err) {
fprintf(stderr, "%s: error registering slot: %s\n", __func__,
--
2.26.2
next prev parent reply other threads:[~2021-01-08 16:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 16:45 [PATCH v4 00/13] KVM: Dirty ring support (QEMU part) Peter Xu
2021-01-08 16:45 ` [PATCH v4 01/13] update-linux-headers: Include const.h Peter Xu
2021-01-08 16:45 ` [PATCH v4 02/13] Update linux headers to 5.11-rc2 Peter Xu
2021-01-08 16:45 ` [PATCH v4 03/13] memory: Introduce log_sync_global() to memory listener Peter Xu
2021-01-08 16:50 ` [PATCH v4 04/13] KVM: Fixup kvm_log_clear_one_slot() ioctl return check Peter Xu
2021-01-08 16:50 ` [PATCH v4 05/13] KVM: Use a big lock to replace per-kml slots_lock Peter Xu
2021-01-08 16:50 ` Peter Xu [this message]
2021-01-08 16:50 ` [PATCH v4 07/13] KVM: Provide helper to get kvm dirty log Peter Xu
2021-01-08 16:50 ` [PATCH v4 08/13] KVM: Provide helper to sync dirty bitmap from slot to ramblock Peter Xu
2021-01-08 16:50 ` [PATCH v4 09/13] KVM: Simplify dirty log sync in kvm_set_phys_mem Peter Xu
2021-01-08 16:50 ` [PATCH v4 10/13] KVM: Cache kvm slot dirty bitmap size Peter Xu
2021-01-08 16:50 ` [PATCH v4 11/13] KVM: Add dirty-gfn-count property Peter Xu
2021-01-08 16:50 ` [PATCH v4 12/13] KVM: Disable manual dirty log when dirty ring enabled Peter Xu
2021-01-08 16:50 ` [PATCH v4 13/13] KVM: Dirty ring support Peter Xu
2021-03-09 21:48 ` [PATCH v4 00/13] KVM: Dirty ring support (QEMU part) 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=20210108165050.406906-3-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=huangy81@chinatelecom.cn \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).