kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	이정석 <jays.lee@samsung.com>, 정성진 <sungjinn.chung@samsung.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/3] migration dirty bitmap support ARMv7
Date: Tue, 15 Apr 2014 10:12:48 +0100	[thread overview]
Message-ID: <534CF810.3020404@arm.com> (raw)
In-Reply-To: <534C8A34.4090606@samsung.com>

Mario,

On 15/04/14 02:24, Mario Smarduch wrote:
> 
> 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(-)
> 

Overall, I think this patch series requires some work, the most glaring
issue being the total lack of documentation (even by my own standards).
Also, it is fairly obvious that ARMv8 should be done at the same time
(as all that code is shared, and will avoid API abuse...), and that a
fair amount of the code is actually generic across architecture, and
should be shared.

I'm very much looking forward to the next iteration of this series.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2014-04-15  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15  1:24 [PATCH 0/3] migration dirty bitmap support ARMv7 Mario Smarduch
2014-04-15  9:12 ` Marc Zyngier [this message]
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=534CF810.3020404@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 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).