linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: kvmarm@lists.cs.columbia.edu
Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, peterx@redhat.com,
	pbonzini@redhat.com, corbet@lwn.net, maz@kernel.org,
	james.morse@arm.com, alexandru.elisei@arm.com,
	suzuki.poulose@arm.com, oliver.upton@linux.dev,
	catalin.marinas@arm.com, will@kernel.org, shuah@kernel.org,
	seanjc@google.com, drjones@redhat.com, dmatlack@google.com,
	bgardon@google.com, ricarkol@google.com, zhenyzha@redhat.com,
	shan.gavin@gmail.com
Subject: [PATCH v1 0/5] KVM: arm64: Enable ring-based dirty memory tracking
Date: Fri, 19 Aug 2022 08:55:56 +0800	[thread overview]
Message-ID: <20220819005601.198436-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").

The generic part has been comprehensive enough, meaning there isn't too
much work, needed to extend it to ARM64. 

- PATCH[1]   enables the feature on ARM64
- PATCH[2-5] improves kvm/selftests/dirty_log_test

Testing
=======

- kvm/selftests/dirty_log_test
- Live migration by QEMU
- Host with 4KB or 64KB base page size

Gavin Shan (5):
  KVM: arm64: Enable ring-based dirty memory tracking
  KVM: selftests: Use host page size to map ring buffer in
    dirty_log_test
  KVM: selftests: Dirty host pages 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               |   2 +-
 arch/arm64/include/uapi/asm/kvm.h            |   1 +
 arch/arm64/kvm/Kconfig                       |   1 +
 arch/arm64/kvm/arm.c                         |   8 ++
 tools/testing/selftests/kvm/dirty_log_test.c | 101 ++++++++++++++-----
 tools/testing/selftests/kvm/lib/kvm_util.c   |   2 +-
 6 files changed, 88 insertions(+), 27 deletions(-)

-- 
2.23.0


             reply	other threads:[~2022-08-19  0:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19  0:55 Gavin Shan [this message]
2022-08-19  0:55 ` [PATCH v1 1/5] KVM: arm64: Enable ring-based dirty memory tracking Gavin Shan
2022-08-19  8:00   ` Marc Zyngier
2022-08-22  1:58     ` Gavin Shan
2022-08-22 18:55       ` Peter Xu
2022-08-23  3:19         ` Gavin Shan
2022-08-22 21:42       ` Marc Zyngier
2022-08-23  5:22         ` Gavin Shan
2022-08-23 13:58           ` Peter Xu
2022-08-23 19:17             ` Marc Zyngier
2022-08-23 21:20               ` Peter Xu
2022-08-23 22:47                 ` Marc Zyngier
2022-08-23 23:19                   ` Peter Xu
2022-08-24 14:45                     ` Marc Zyngier
2022-08-24 16:21                       ` Peter Xu
2022-08-24 20:57                         ` Marc Zyngier
2022-08-26  6:05                           ` Gavin Shan
2022-08-26 10:50                   ` Paolo Bonzini
2022-08-26 15:49                     ` Marc Zyngier
2022-08-27  8:27                       ` Paolo Bonzini
2022-08-23 14:44         ` Oliver Upton
2022-08-23 20:35           ` Marc Zyngier
2022-08-26 10:58             ` Paolo Bonzini
2022-08-26 15:28               ` Marc Zyngier
2022-08-30 14:42                 ` Peter Xu
2022-09-02  0:19                   ` Paolo Bonzini
2022-08-19  0:55 ` [PATCH v1 2/5] KVM: selftests: Use host page size to map ring buffer in dirty_log_test Gavin Shan
2022-08-19  0:55 ` [PATCH v1 3/5] KVM: selftests: Dirty host pages " Gavin Shan
2022-08-19  5:28   ` Andrew Jones
2022-08-22  6:29     ` Gavin Shan
2022-08-23  3:09       ` Gavin Shan
2022-08-19  0:56 ` [PATCH v1 4/5] KVM: selftests: Clear dirty ring states between two modes " Gavin Shan
2022-08-19  0:56 ` [PATCH v1 5/5] KVM: selftests: Automate choosing dirty ring size " 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=20220819005601.198436-1-gshan@redhat.com \
    --to=gshan@redhat.com \
    --cc=alexandru.elisei@arm.com \
    --cc=bgardon@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=dmatlack@google.com \
    --cc=drjones@redhat.com \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=ricarkol@google.com \
    --cc=seanjc@google.com \
    --cc=shan.gavin@gmail.com \
    --cc=shuah@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --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: 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).