From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MO2qp-0007fi-2U
	for qemu-devel@nongnu.org; Tue, 07 Jul 2009 01:04:19 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MO2qk-0007e1-NC
	for qemu-devel@nongnu.org; Tue, 07 Jul 2009 01:04:18 -0400
Received: from [199.232.76.173] (port=57982 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MO2qk-0007dy-Ch
	for qemu-devel@nongnu.org; Tue, 07 Jul 2009 01:04:14 -0400
Received: from mx2.redhat.com ([66.187.237.31]:43537)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1MO2qj-000452-Np
	for qemu-devel@nongnu.org; Tue, 07 Jul 2009 01:04:13 -0400
Message-ID: <4A52D6C5.2010406@redhat.com>
Date: Tue, 07 Jul 2009 08:01:57 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 0/4] Machine config files
References: <20090610173803.4674.82538.stgit@wren.home>
	<4A5225D6.8030102@redhat.com> <4A52284C.9080604@redhat.com>
	<200907061750.20116.paul@codesourcery.com>
In-Reply-To: <200907061750.20116.paul@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Paul Brook <paul@codesourcery.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>

On 07/06/2009 07:47 PM, Paul Brook wrote:
>> 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.
>    

These features are logically orthogonal and initiated by different 
users, so it will be seen as if hotplug randomly has high latency.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.