From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MNrOh-0003oQ-Jr
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 12:50:31 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MNrOd-0003ir-PI
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 12:50:31 -0400
Received: from [199.232.76.173] (port=47783 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MNrOd-0003i0-8y
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 12:50:27 -0400
Received: from mx20.gnu.org ([199.232.41.8]:15798)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1MNrOc-0003e4-SS
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 12:50:27 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1MNrOZ-0003Sn-MO
	for qemu-devel@nongnu.org; Mon, 06 Jul 2009 12:50:24 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Re: [PATCH 0/4] Machine config files
Date: Mon, 6 Jul 2009 17:47:53 +0100
References: <20090610173803.4674.82538.stgit@wren.home>
	<4A5225D6.8030102@redhat.com> <4A52284C.9080604@redhat.com>
In-Reply-To: <4A52284C.9080604@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907061750.20116.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.gnu.org/pipermail/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: Jan Kiszka <jan.kiszka@siemens.com>, "Michael S. Tsirkin" <mst@redhat.com>, Avi Kivity <avi@redhat.com>, Markus Armbruster <armbru@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>

> >>> I suspect it isn't enougth to make it work though, you still need to
> >>> know the position of the device in the device tree. To answer
> >>> questions like "is your pci device behind a bridge and if so which
> >>> one?".
> >>
> >> Isn't that info provided by qdev?
> >
> > Yep, it is.
> >
> > Serialize qdev tree (into fdt or whatever else), send it over wire
> > first, recreate qdev tree on the other side (including save/load
> > callback registration), then parse everything else.  That is how I
> > wanna have it work some day ...
>
> Slight change: instead of serializing into a tree, have a qdev callback
> which generates an add event that can be sent over the wire.  While
> migrating, additional hotplug simply call the same callback and the
> hotplug is migrated in real time.

I think this is just going to cause you problems. Way simpler to just disable 
changing the machine configuration while migration is in progress.

Paul