From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55823)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1V1ZNa-0006Sz-7b
	for qemu-devel@nongnu.org; Tue, 23 Jul 2013 05:59:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1V1ZNZ-0001QR-3H
	for qemu-devel@nongnu.org; Tue, 23 Jul 2013 05:59:38 -0400
Received: from cantor2.suse.de ([195.135.220.15]:33598 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1V1ZNY-0001QJ-Su
	for qemu-devel@nongnu.org; Tue, 23 Jul 2013 05:59:37 -0400
Message-ID: <51EE5405.3020109@suse.de>
Date: Tue, 23 Jul 2013 11:59:33 +0200
From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>
MIME-Version: 1.0
References: <25C84044-9F40-4076-BDAB-03363073B671@cs2c.com.cn>
	<20130723085146.GA2695@stefanha-thinkpad.redhat.com>
	<F6ACEFCD-79B5-4105-ABC7-559245226874@cs2c.com.cn>
	<51EE4D4B.3070808@suse.de>
	<67E6C951-BB76-493D-AD1D-09F34512C3AF@cs2c.com.cn>
In-Reply-To: <67E6C951-BB76-493D-AD1D-09F34512C3AF@cs2c.com.cn>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH 0/3] dataplane: virtio-blk live migration
 with	x-data-plane=on
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: yinyin <yin.yin@cs2c.com.cn>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>

Am 23.07.2013 11:43, schrieb yinyin:
> =E5=9C=A8 2013-7-23=EF=BC=8C=E4=B8=8B=E5=8D=885:30=EF=BC=8CAndreas F=C3=
=A4rber <afaerber@suse.de> =E5=86=99=E9=81=93=EF=BC=9A
>> Am 23.07.2013 11:19, schrieb yinyin:
>>> 	during the migration, the source, not the destination, will start da=
taplane again....
>>> 	I think the process of migration with dataplane as follows:
>>> 1. migration begin to start
>>> 2. the migration source stop the dataplane
>>> 3. do migration ...
>>> 4. migration completed, the destination start the dataplane.
>>
>> I can't speak for the dataplane, but in general the source guest is
>> expected to continue working during live migration (that's the "live"
>> part) until it has been fully transferred to the destination.
>=20
> when dataplane stop, the source guest can continue work, but not use da=
taplane thread.

So how would it do I/O then?

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC=
rnberg