From: Marc Zyngier <marc.zyngier@arm.com>
To: Mario Smarduch <m.smarduch@samsung.com>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
이정석 <jays.lee@samsung.com>, 정성진 <sungjinn.chung@samsung.com>
Subject: Re: [PATCH 0/5] live migration dirty bitmap support for ARMv7
Date: Thu, 17 Apr 2014 08:18:28 +0100 [thread overview]
Message-ID: <87ioq8xw3f.fsf@approximate.cambridge.arm.com> (raw)
In-Reply-To: <534F2F26.5040706@samsung.com> (Mario Smarduch's message of "Thu, 17 Apr 2014 02:32:22 +0100")
Hi Mario,
On Thu, Apr 17 2014 at 2:32:22 am BST, Mario Smarduch <m.smarduch@samsung.com> wrote:
> Revised iteration after initial comments. Still just for ARMv7. I looked
> at the ARMv8 code and yes it practically appears to reuse most of
> fault handling in ARMv7, I wasn't aware so much code was in common.
> But before then want to make sure it's reliable on real hardware.
>
> This patch adds support for ARMv7 Live Migration, primarily dirty bit map
> management is added. The patch follows the normal migration flow managed by
> user space, first write protecting the entire address space and later
> keeping track of dirty pages. In the process of initial write protection,
> and first time faults huge pages are broken up into small pages to support
> migration on loaded systems.
Thanks for respining this. A few words about the patch submission
process though:
- Please add a version number (v2, v3...) to your patch series. It helps
the reviewers keeping track of where we are in the review process
- Add a change log to your cover letter. Clearly state what
changed. Otherwise, reviewers have to start diffing between patches,
which becomes quickly messy, specially considering the lack of
versioning.
- Make sure your patches are part of an email thread starting with your
cover letter. This helps reviewers to locate the various patches in a
busy Inbox, and to follow the evolution of a discussion. Use of "git
send-email" is recommended for posting the patch series.
That being said, I'm off to review the actual patches... ;-)
Thanks,
M.
> Mario Smarduch (5):
> add ARMv7 HYP API to flush VM TLBs without address param
> live migration support for initial write protect of VM to manage
> dirty pages
> live migration support for VM dirty log management
> add 2nd stage page fault handling during live migration
> add kvm_arch glogal live migration variable
>
> arch/arm/include/asm/kvm_asm.h | 1 +
> arch/arm/include/asm/kvm_host.h | 7 ++
> arch/arm/kvm/arm.c | 75 ++++++++++++-
> arch/arm/kvm/interrupts.S | 5 +
> arch/arm/kvm/mmu.c | 220 ++++++++++++++++++++++++++++++++++++++-
> 5 files changed, 305 insertions(+), 3 deletions(-)
--
Jazz is not dead. It just smells funny.
prev parent reply other threads:[~2014-04-17 7:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 1:32 [PATCH 0/5] live migration dirty bitmap support for ARMv7 Mario Smarduch
2014-04-17 7:18 ` Marc Zyngier [this message]
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=87ioq8xw3f.fsf@approximate.cambridge.arm.com \
--to=marc.zyngier@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=jays.lee@samsung.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=m.smarduch@samsung.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.