From: Mario Smarduch <m.smarduch@samsung.com>
To: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Marc Zyngier <marc.zyngier@arm.com>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>
Cc: 이정석 <jays.lee@samsung.com>, 정성진 <sungjinn.chung@samsung.com>,
gavin.guo@canonical.com,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [PATCH v3 0/4] live migration dirty bitmap support for ARMv7
Date: Tue, 22 Apr 2014 16:17:39 -0700 [thread overview]
Message-ID: <5356F893.5020207@samsung.com> (raw)
Hi,
this the third iteration of live migration support for the time being on
ARMv7. The patches depend on Eric Augers patch for memory regions.
Changes since v2:
- move initial VM write protect to memory region architecture prepare function
(needed to make dirty logging function generic)
- added stage2_mark_pte_ro() - to mark ptes ro - Marc's comment
- optimized initial VM memory region write protect to do fewer table lookups -
applied Marc's comment for walking dirty bitmap mask
- added pud_addr_end() for stage2 tables, to make the walk 4-level
- added kvm_flush_remote_tlbs() to use ARM TLB invalidation, made the generic
one weak, Marc's comment to for generic dirty bitmap log function
- optimized walking dirty bit map mask to skip upper tables - Marc's comment
- deleted x86,arm kvm_vm_ioctl_get_dirty_log(), moved to kvm_main.c tagged
the function weak - Marc's comment
- changed Data Abort handler pte index handling - Marc's comment
Mario Smarduch (4):
add ARMv7 HYP API to flush VM TLBs without address param
live migration support for initial write protect of VM to track dirty
pages
live migration support for VM dirty log management
add 2nd stage page fault handling during live migration
arch/arm/include/asm/kvm_asm.h | 1 +
arch/arm/include/asm/kvm_host.h | 13 ++
arch/arm/kvm/arm.c | 8 +-
arch/arm/kvm/interrupts.S | 5 +
arch/arm/kvm/mmu.c | 303 ++++++++++++++++++++++++++++++++++++++-
arch/x86/kvm/x86.c | 78 ----------
virt/kvm/kvm_main.c | 87 ++++++++++-
7 files changed, 409 insertions(+), 86 deletions(-)
--
1.7.9.5
reply other threads:[~2014-04-22 23:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5356F893.5020207@samsung.com \
--to=m.smarduch@samsung.com \
--cc=christoffer.dall@linaro.org \
--cc=gavin.guo@canonical.com \
--cc=jays.lee@samsung.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=sungjinn.chung@samsung.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