| Message ID | 20221031003621.164306-1-gshan@redhat.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | KVM: arm64: Enable ring-based dirty memory tracking | expand |
On Mon, 31 Oct 2022 08:36:12 +0800, Gavin Shan wrote: > This series enables the ring-based dirty memory tracking for ARM64. > The feature has been available and enabled on x86 for a while. It > is beneficial when the number of dirty pages is small in a checkpointing > system or live migration scenario. More details can be found from > fb04a1eddb1a ("KVM: X86: Implement ring-based dirty memory tracking"). > > v6: https://lore.kernel.org/kvmarm/20221011061447.131531-1-gshan@redhat.com/ > v5: https://lore.kernel.org/all/20221005004154.83502-1-gshan@redhat.com/ > v4: https://lore.kernel.org/kvmarm/20220927005439.21130-1-gshan@redhat.com/ > v3: https://lore.kernel.org/r/20220922003214.276736-1-gshan@redhat.com > v2: https://lore.kernel.org/lkml/YyiV%2Fl7O23aw5aaO@xz-m1.local/T/ > v1: https://lore.kernel.org/lkml/20220819005601.198436-1-gshan@redhat.com > > [...] Applied to fixes, thanks! [3/9] KVM: Check KVM_CAP_DIRTY_LOG_{RING, RING_ACQ_REL} prior to enabling them commit: 7a2726ec3290c52f52ce8d5f5af73ab8c7681bc1 Cheers, M.
This series enables the ring-based dirty memory tracking for ARM64. The feature has been available and enabled on x86 for a while. It is beneficial when the number of dirty pages is small in a checkpointing system or live migration scenario. More details can be found from fb04a1eddb1a ("KVM: X86: Implement ring-based dirty memory tracking"). v6: https://lore.kernel.org/kvmarm/20221011061447.131531-1-gshan@redhat.com/ v5: https://lore.kernel.org/all/20221005004154.83502-1-gshan@redhat.com/ v4: https://lore.kernel.org/kvmarm/20220927005439.21130-1-gshan@redhat.com/ v3: https://lore.kernel.org/r/20220922003214.276736-1-gshan@redhat.com v2: https://lore.kernel.org/lkml/YyiV%2Fl7O23aw5aaO@xz-m1.local/T/ v1: https://lore.kernel.org/lkml/20220819005601.198436-1-gshan@redhat.com Testing ======= (1) kvm/selftests/dirty_log_test (2) Live migration by QEMU Changelog ========= v7: * Cut down #ifdef, avoid using 'container_of()', move the dirty-ring check after KVM_REQ_VM_DEAD, add comments for kvm_dirty_ring_check_request(), use tab character for KVM event definitions in kvm_host.h in PATCH[v7 01] (Sean) * Add PATCH[v7 03] to recheck if the capability has been advertised prior to enable RING/RING_ACEL_REL (Sean) * Improve the description about capability RING_WITH_BITMAP, rename kvm_dirty_ring_exclusive() to kvm_use_dirty_bitmap() in PATCH[v7 04/09] (Peter/Oliver/Sean) * Add PATCH[v7 05/09] to improve no-running-vcpu report (Marc/Sean) * Improve commit messages (Sean/Oliver) v6: * Add CONFIG_HAVE_KVM_DIRTY_RING_WITH_BITMAP, for arm64 to advertise KVM_CAP_DIRTY_RING_WITH_BITMAP in PATCH[v6 3/8] (Oliver/Peter) * Add helper kvm_dirty_ring_exclusive() to check if traditional bitmap-based dirty log tracking is exclusive to dirty-ring in PATCH[v6 3/8] (Peter) * Enable KVM_CAP_DIRTY_RING_WITH_BITMAP in PATCH[v6 5/8] (Gavin) v5: * Drop empty stub kvm_dirty_ring_check_request() (Marc/Peter) * Add PATCH[v5 3/7] to allow using bitmap, indicated by KVM_CAP_DIRTY_LOG_RING_ALLOW_BITMAP (Marc/Peter) v4: * Commit log improvement (Marc) * Add helper kvm_dirty_ring_check_request() (Marc) * Drop ifdef for kvm_cpu_dirty_log_size() (Marc) v3: * Check KVM_REQ_RING_SOFT_RULL inside kvm_request_pending() (Peter) * Move declaration of kvm_cpu_dirty_log_size() (test-robot) v2: * Introduce KVM_REQ_RING_SOFT_FULL (Marc) * Changelog improvement (Marc) * Fix dirty_log_test without knowing host page size (Drew) Gavin Shan (9): KVM: x86: Introduce KVM_REQ_DIRTY_RING_SOFT_FULL KVM: Move declaration of kvm_cpu_dirty_log_size() to kvm_dirty_ring.h KVM: Check KVM_CAP_DIRTY_LOG_{RING, RING_ACQ_REL} prior to enabling them KVM: Support dirty ring in conjunction with bitmap KVM: arm64: Improve no-running-vcpu report for dirty ring KVM: arm64: Enable ring-based dirty memory tracking KVM: selftests: Use host page size to map ring buffer in dirty_log_test KVM: selftests: Clear dirty ring states between two modes in dirty_log_test KVM: selftests: Automate choosing dirty ring size in dirty_log_test Documentation/virt/kvm/api.rst | 33 +++++++++--- arch/arm64/include/uapi/asm/kvm.h | 1 + arch/arm64/kvm/Kconfig | 2 + arch/arm64/kvm/arm.c | 3 ++ arch/arm64/kvm/mmu.c | 14 ++++++ arch/arm64/kvm/vgic/vgic-init.c | 4 +- arch/arm64/kvm/vgic/vgic-irqfd.c | 4 +- arch/arm64/kvm/vgic/vgic-its.c | 2 +- arch/arm64/kvm/vgic/vgic-mmio-v3.c | 18 ++----- arch/arm64/kvm/vgic/vgic.c | 10 ++++ arch/arm64/kvm/vgic/vgic.h | 1 - arch/x86/include/asm/kvm_host.h | 2 - arch/x86/kvm/x86.c | 15 +++--- include/kvm/arm_vgic.h | 1 + include/linux/kvm_dirty_ring.h | 25 +++++---- include/linux/kvm_host.h | 10 ++-- include/uapi/linux/kvm.h | 1 + tools/testing/selftests/kvm/dirty_log_test.c | 53 ++++++++++++++------ tools/testing/selftests/kvm/lib/kvm_util.c | 2 +- virt/kvm/Kconfig | 8 +++ virt/kvm/dirty_ring.c | 44 ++++++++++++++-- virt/kvm/kvm_main.c | 39 +++++++++----- 22 files changed, 208 insertions(+), 84 deletions(-)