From: Mario Smarduch <m.smarduch@samsung.com>
To: kvmarm@lists.cs.columbia.edu, christoffer.dall@linaro.org,
marc.zyngier@arm.com, 이정석 <jays.lee@samsung.com>,
정성진 <sungjinn.chung@samsung.com>
Cc: kvm@vger.kernel.org
Subject: [PATCH 0/3] migration dirty bitmap support ARMv7
Date: Mon, 14 Apr 2014 18:24:04 -0700 [thread overview]
Message-ID: <534C8A34.4090606@samsung.com> (raw)
The patch set supports migration dirty bitmap support implementation for
arm-kvm. Spliting of pmd's to pte's as suggested is implemented on demand
when migration is started.
I tested it on 4-way SMP ARMv7, with SMP guests.
2GB VMs with dirty shared memory segments upto 1.8 GB
and relatively fast update rates 16Mb/5mS.
Next course of action would be rmap support which
scales much better on bigger systems. Although one
think that confused me, x86 migrations were sometimes
10 to 15 times slower, I think it must be something
wrong with my configuration.
Mario Smarduch (3):
headers for migration dirtybitmap support
initial write protect of VM address space and on dirty log read
hooks to interface with QEMU for initial write protect, dirty log read
arch/arm/include/asm/kvm_host.h | 9 +++
arch/arm/kvm/arm.c | 62 ++++++++++++++-
arch/arm/kvm/mmu.c | 158 ++++++++++++++++++++++++++++++++++++++-
3 files changed, 226 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-04-15 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 1:24 Mario Smarduch [this message]
2014-04-15 9:12 ` [PATCH 0/3] migration dirty bitmap support ARMv7 Marc Zyngier
2014-04-15 17:22 ` Mario Smarduch
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=534C8A34.4090606@samsung.com \
--to=m.smarduch@samsung.com \
--cc=christoffer.dall@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.