From: Mario Smarduch <m.smarduch@samsung.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu, marc.zyngier@arm.com,
steve.capper@arm.com, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, gavin.guo@canonical.com,
peter.maydell@linaro.org, jays.lee@samsung.com,
sungjinn.chung@samsung.com
Subject: Re: [PATCH v6 2/4] live migration support for initial write protect of VM
Date: Tue, 27 May 2014 13:15:46 -0700 [thread overview]
Message-ID: <5384F272.9020401@samsung.com> (raw)
In-Reply-To: <20140527195803.GB16428@lvm>
Hi Christoffer,
I was out traveling last week + holiday.
You had lots of comments in last version (incl. below), reworking to submit a
new series. Un-clutter from basic issues, and update current logic. In next
couple days I'll submit new series.
Also looking into a wiki to document test env (but may windup with a github link).
Thanks,
Mario
On 05/27/2014 12:58 PM, Christoffer Dall wrote:
> On Thu, May 15, 2014 at 11:27:29AM -0700, Mario Smarduch wrote:
>> Patch adds memslot support for initial write protection and split up of huge
>> pages
>
> I lost track of where we are with these patches, but I see a lot of
> issues in this patch that I believe I already commented on (but I may
> not have had time to comment before you sent out v6).
>
> In any case, I'm going to wait with reviewing things carefully until you
> send out a v7, but for v7:
> - Please document the rationale and design behind what you're doing in
> the commit text of each patch. Each of these patches are quite
> large, but the commit messages are barely two lines. I suggest you
> take a look at 'git log arch/arm/kvm' for example to get a feel for
> what I'm looking for.
>
> - There is nothing specific in the interface to KVM discussing
> migration or live migration, it is only used as an example for
> features in trying to stay generic. Please use similar generic
> concepts in the kernel to make things coherent. 'git grep
> migration arch/x86/kvm' also tells you that x86 gets away with full
> support for live migration without referring to migration except as
> examples of how features might be useful.
>
> Thanks for the work, looking forward to seeing a new revision.
>
> -Christoffer
>
next prev parent reply other threads:[~2014-05-27 20:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 18:27 [PATCH v6 0/4] live migration dirty bitmap support for ARMv7 Mario Smarduch
2014-05-15 18:27 ` [PATCH v6 1/4] add ARMv7 HYP API to flush VM TLBs without address param Mario Smarduch
2014-05-27 19:51 ` Christoffer Dall
2014-05-15 18:27 ` [PATCH v6 2/4] live migration support for initial write protect of VM Mario Smarduch
2014-05-27 19:58 ` Christoffer Dall
2014-05-27 20:15 ` Mario Smarduch [this message]
2014-05-27 20:20 ` Christoffer Dall
2014-05-15 18:27 ` [PATCH v6 3/4] live migration support for VM dirty log management Mario Smarduch
2014-05-27 20:12 ` Christoffer Dall
2014-05-27 21:55 ` Mario Smarduch
2014-05-28 9:08 ` Christoffer Dall
2014-05-28 17:59 ` Mario Smarduch
2014-05-15 18:27 ` [PATCH v6 4/4] add 2nd stage page fault handling during live migration Mario Smarduch
2014-05-27 20:19 ` Christoffer Dall
2014-05-28 1:30 ` Mario Smarduch
2014-05-28 8:09 ` Christoffer Dall
2014-05-28 17:55 ` Mario Smarduch
2014-05-28 18:42 ` Mario Smarduch
2014-05-29 2:02 ` Mario Smarduch
2014-05-29 8:42 ` Christoffer Dall
2014-05-29 8:51 ` Christoffer Dall
2014-05-29 17:08 ` Mario Smarduch
2014-05-29 17:57 ` Christoffer Dall
2014-05-29 19:10 ` Mario Smarduch
2014-05-15 18:51 ` [PATCH v6 0/4] live migration dirty bitmap support for ARMv7 Christoffer Dall
2014-05-15 22:53 ` 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=5384F272.9020401@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=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--cc=steve.capper@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