From: Keqian Zhu <zhukeqian1@huawei.com>
To: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>
Cc: Marc Zyngier <maz@kernel.org>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Jay Zhou <jianjay.zhou@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Will Deacon <will@kernel.org>
Subject: [PATCH 0/3] KVM: arm64: Some optimizations about enabling dirty log
Date: Wed, 25 Mar 2020 12:24:20 +0800 [thread overview]
Message-ID: <20200325042423.12181-1-zhukeqian1@huawei.com> (raw)
This patch series is for "queue" branch of [1] and based on patches[2].
It brings obvious time decreasement for migration with different page
size.
The QEMU counterpart will be sent out later, thanks.
[1] git://git.kernel.org/pub/scm/virt/kvm/kvm.git
[2] https://lore.kernel.org/kvm/20200227013227.1401-1-jianjay.zhou@huawei.com/
Keqian Zhu (3):
KVM/memslot: Move the initial set of dirty bitmap to arch
KVM/arm64: Support enabling dirty log graually in small chunks
KVM/arm64: Only set bits of dirty bitmap with valid translation
entries
Documentation/virt/kvm/api.rst | 2 +-
arch/arm/include/asm/kvm_host.h | 2 -
arch/arm64/include/asm/kvm_host.h | 5 +-
arch/x86/kvm/x86.c | 3 +
virt/kvm/arm/mmu.c | 175 +++++++++++++++++++++++++-----
virt/kvm/kvm_main.c | 3 -
6 files changed, 157 insertions(+), 33 deletions(-)
--
2.19.1
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2020-03-25 4:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 4:24 Keqian Zhu [this message]
2020-03-25 4:24 ` [PATCH 1/3] KVM/memslot: Move the initial set of dirty bitmap to arch Keqian Zhu
2020-03-25 4:24 ` [PATCH 2/3] KVM/arm64: Support enabling dirty log gradually in small chunks Keqian Zhu
2020-03-25 4:24 ` [PATCH 3/3] KVM/arm64: Only set bits of dirty bitmap with valid translation entries Keqian Zhu
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=20200325042423.12181-1-zhukeqian1@huawei.com \
--to=zhukeqian1@huawei.com \
--cc=jianjay.zhou@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=will@kernel.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).