From: Gavin Shan <gshan@redhat.com> To: kvmarm@lists.linux.dev Cc: kvm@vger.kernel.org, catalin.marinas@arm.com, andrew.jones@linux.dev, will@kernel.org, shan.gavin@gmail.com, bgardon@google.com, dmatlack@google.com, pbonzini@redhat.com, zhenyzha@redhat.com, shuah@kernel.org, kvmarm@lists.cs.columbia.edu Subject: [PATCH v5 0/7] KVM: arm64: Enable ring-based dirty memory tracking Date: Wed, 5 Oct 2022 08:41:47 +0800 [thread overview] Message-ID: <20221005004154.83502-1-gshan@redhat.com> (raw) 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"). This series is applied on top of Marc's v2 series [0], fixing dirty-ring ordering issue. This series is going to land on v6.1.rc0 pretty soon. [0] https://lore.kernel.org/kvmarm/20220926145120.27974-1-maz@kernel.org 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 ========= 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 (7): KVM: x86: Introduce KVM_REQ_RING_SOFT_FULL KVM: x86: Move declaration of kvm_cpu_dirty_log_size() to kvm_dirty_ring.h KVM: x86: Allow to use bitmap in ring-based dirty page tracking 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 | 19 ++++--- arch/arm64/include/uapi/asm/kvm.h | 1 + arch/arm64/kvm/Kconfig | 1 + arch/arm64/kvm/arm.c | 3 ++ arch/x86/include/asm/kvm_host.h | 2 - arch/x86/kvm/x86.c | 15 +++--- include/linux/kvm_dirty_ring.h | 9 ++-- include/linux/kvm_host.h | 1 + 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/dirty_ring.c | 19 ++++++- virt/kvm/kvm_main.c | 24 ++++----- 13 files changed, 92 insertions(+), 58 deletions(-) -- 2.23.0 _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Gavin Shan <gshan@redhat.com> To: kvmarm@lists.linux.dev Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, peterx@redhat.com, catalin.marinas@arm.com, bgardon@google.com, shuah@kernel.org, andrew.jones@linux.dev, will@kernel.org, dmatlack@google.com, pbonzini@redhat.com, zhenyzha@redhat.com, james.morse@arm.com, suzuki.poulose@arm.com, alexandru.elisei@arm.com, oliver.upton@linux.dev, seanjc@google.com, shan.gavin@gmail.com Subject: [PATCH v5 0/7] KVM: arm64: Enable ring-based dirty memory tracking Date: Wed, 5 Oct 2022 08:41:47 +0800 [thread overview] Message-ID: <20221005004154.83502-1-gshan@redhat.com> (raw) Message-ID: <20221005004147.w8iS3kamin_Pvn3dIniDlfI-J6BwTE71jMJpBCyDvXc@z> (raw) 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"). This series is applied on top of Marc's v2 series [0], fixing dirty-ring ordering issue. This series is going to land on v6.1.rc0 pretty soon. [0] https://lore.kernel.org/kvmarm/20220926145120.27974-1-maz@kernel.org 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 ========= 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 (7): KVM: x86: Introduce KVM_REQ_RING_SOFT_FULL KVM: x86: Move declaration of kvm_cpu_dirty_log_size() to kvm_dirty_ring.h KVM: x86: Allow to use bitmap in ring-based dirty page tracking 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 | 19 ++++--- arch/arm64/include/uapi/asm/kvm.h | 1 + arch/arm64/kvm/Kconfig | 1 + arch/arm64/kvm/arm.c | 3 ++ arch/x86/include/asm/kvm_host.h | 2 - arch/x86/kvm/x86.c | 15 +++--- include/linux/kvm_dirty_ring.h | 9 ++-- include/linux/kvm_host.h | 1 + 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/dirty_ring.c | 19 ++++++- virt/kvm/kvm_main.c | 24 ++++----- 13 files changed, 92 insertions(+), 58 deletions(-) -- 2.23.0
next reply other threads:[~2022-10-05 0:43 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-05 0:41 Gavin Shan [this message] 2022-10-05 0:41 ` [PATCH v5 0/7] KVM: arm64: Enable ring-based dirty memory tracking Gavin Shan 2022-10-05 0:41 ` [PATCH v5 1/7] KVM: x86: Introduce KVM_REQ_RING_SOFT_FULL Gavin Shan 2022-10-05 0:41 ` Gavin Shan 2022-10-05 0:41 ` [PATCH v5 2/7] KVM: x86: Move declaration of kvm_cpu_dirty_log_size() to kvm_dirty_ring.h Gavin Shan 2022-10-05 0:41 ` Gavin Shan 2022-10-05 0:41 ` [PATCH v5 3/7] KVM: x86: Allow to use bitmap in ring-based dirty page tracking Gavin Shan 2022-10-05 0:41 ` Gavin Shan 2022-10-06 20:28 ` Peter Xu 2022-10-06 20:28 ` Peter Xu 2022-10-06 23:38 ` Gavin Shan 2022-10-06 23:38 ` Gavin Shan 2022-10-07 14:31 ` Peter Xu 2022-10-07 14:31 ` Peter Xu 2022-10-10 23:18 ` Oliver Upton 2022-10-10 23:18 ` Oliver Upton 2022-10-10 23:43 ` Oliver Upton 2022-10-10 23:43 ` Oliver Upton 2022-10-10 23:49 ` Peter Xu 2022-10-10 23:49 ` Peter Xu 2022-10-10 23:58 ` Gavin Shan 2022-10-10 23:58 ` Gavin Shan 2022-10-10 23:58 ` Oliver Upton 2022-10-10 23:58 ` Oliver Upton 2022-10-11 0:20 ` Peter Xu 2022-10-11 0:20 ` Peter Xu 2022-10-11 1:12 ` Oliver Upton 2022-10-11 1:12 ` Oliver Upton 2022-10-11 3:56 ` Gavin Shan 2022-10-11 3:56 ` Gavin Shan 2022-10-11 6:31 ` Gavin Shan 2022-10-11 6:31 ` Gavin Shan 2022-10-14 16:55 ` Peter Xu 2022-10-14 16:55 ` Peter Xu 2022-10-18 7:38 ` Oliver Upton 2022-10-18 7:38 ` Oliver Upton 2022-10-18 7:40 ` Oliver Upton 2022-10-18 7:40 ` Oliver Upton 2022-10-18 15:50 ` Peter Xu 2022-10-18 15:50 ` Peter Xu 2022-10-05 0:41 ` [PATCH v5 4/7] KVM: arm64: Enable ring-based dirty memory tracking Gavin Shan 2022-10-05 0:41 ` Gavin Shan 2022-10-05 0:41 ` [PATCH v5 5/7] KVM: selftests: Use host page size to map ring buffer in dirty_log_test Gavin Shan 2022-10-05 0:41 ` Gavin Shan 2022-10-05 0:41 ` [PATCH v5 6/7] KVM: selftests: Clear dirty ring states between two modes " Gavin Shan 2022-10-05 0:41 ` Gavin Shan 2022-10-05 0:41 ` [PATCH v5 7/7] KVM: selftests: Automate choosing dirty ring size " Gavin Shan 2022-10-05 0:41 ` Gavin Shan
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=20221005004154.83502-1-gshan@redhat.com \ --to=gshan@redhat.com \ --cc=andrew.jones@linux.dev \ --cc=bgardon@google.com \ --cc=catalin.marinas@arm.com \ --cc=dmatlack@google.com \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=kvmarm@lists.linux.dev \ --cc=pbonzini@redhat.com \ --cc=shan.gavin@gmail.com \ --cc=shuah@kernel.org \ --cc=will@kernel.org \ --cc=zhenyzha@redhat.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: linkBe 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).