From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=59183 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PN7NY-00077N-Ek
	for qemu-devel@nongnu.org; Mon, 29 Nov 2010 12:19:05 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paul@codesourcery.com>) id 1PN7NW-0003ra-J3
	for qemu-devel@nongnu.org; Mon, 29 Nov 2010 12:19:04 -0500
Received: from mail.codesourcery.com ([38.113.113.100]:33596)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paul@codesourcery.com>) id 1PN7NW-0003rG-BW
	for qemu-devel@nongnu.org; Mon, 29 Nov 2010 12:19:02 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 00/21] Kemari for KVM 0.2
Date: Mon, 29 Nov 2010 17:18:42 +0000
References: <1290665220-26478-1-git-send-email-tamura.yoshiaki@lab.ntt.co.jp>
	<201011291653.42595.paul@codesourcery.com>
	<4CF3DD61.2010102@codemonkey.ws>
In-Reply-To: <4CF3DD61.2010102@codemonkey.ws>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201011291718.42500.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: ohmura.kei@lab.ntt.co.jp, dlaor@redhat.com, stefanha@linux.vnet.ibm.com, kvm@vger.kernel.org, Stefan Hajnoczi <stefanha@gmail.com>, mtosatti@redhat.com, Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>, vatsa@linux.vnet.ibm.com, Blue Swirl <blauwirbel@gmail.com>, aliguori@us.ibm.com, avi@redhat.com, psuriset@linux.vnet.ibm.com, ananth@in.ibm.com

> On 11/29/2010 10:53 AM, Paul Brook wrote:
> >>> Is this a fair summary: any device that supports live migration workw
> >>> under Kemari?
> >> 
> >> It might be fair summary but practically we barely have live migration
> >> working w/o Kemari. In addition, last I checked Kemari needs additional
> >> hooks and it will be too hard to keep that out of tree until all devices
> >> get it.
> > 
> > That's not what I've been hearing earlier in this thread.
> > The responses from Yoshi indicate that Stefan's summary is correct.  i.e.
> > the current Kemari implementation may require per-device hooks, but
> > that's a bug and should be fixed before merging.
> 
> It's actually really important that Kemari make use of an intermediate
> layer such that the hooks can distinguish between a device access and a
> recursive access.

I'm failing to understand how this is anything other than running sed over 
block/*.c (or hw/*.c, depending whether you choose to rename the internal or 
external API).

Paul