From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
Mario Smarduch <m.smarduch@samsung.com>
Cc: "eric.auger@linaro.org" <eric.auger@linaro.org>,
"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 3/3] migration dirtybitmap support ARMv7
Date: Wed, 16 Apr 2014 10:51:35 +0200 [thread overview]
Message-ID: <534E4497.2050006@de.ibm.com> (raw)
In-Reply-To: <534E3BA6.4050503@arm.com>
On 16/04/14 10:13, Marc Zyngier wrote:
> Hi Mario,
>
> On 16/04/14 02:24, Mario Smarduch wrote:
>> Hi Eric, Mark -
>> what repository should I use to pick up Eric patches?
>
> The initial posting was there:
>
> https://lists.cs.columbia.edu/pipermail/kvmarm/2014-April/008791.html
>
> Reading Eric's patch again, it is not doing exactly the same thing, but
> actually dealing with a slightly different (but connected) case.
>
> I suggest you both work together on a common patch (or patch series)
> that deals with the various memory region change thingy.
>
>> For kvm_vm_ioctl_get_dirty_log() not sure what to make generic
>> it appears generic enough and it does what it needs to do?
>
> What I'm saying is that it should be put in a common location
> (virt/kvm/kvm_main.c?), possibly as a weak symbol so it can be
> overridden by other architectures.
Yes, make it weak. The s390 implementation looks different.
prev parent reply other threads:[~2014-04-16 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 1:24 [PATCH 3/3] migration dirtybitmap support ARMv7 Mario Smarduch
2014-04-15 9:06 ` Marc Zyngier
2014-04-16 1:24 ` Mario Smarduch
2014-04-16 8:13 ` Marc Zyngier
2014-04-16 8:51 ` Christian Borntraeger [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=534E4497.2050006@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=jays.lee@samsung.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=m.smarduch@samsung.com \
--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.