From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:52069)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1UDeYd-0000bH-78
	for qemu-devel@nongnu.org; Thu, 07 Mar 2013 12:24:45 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1UDeYc-0001wH-1X
	for qemu-devel@nongnu.org; Thu, 07 Mar 2013 12:24:43 -0500
Received: from mx1.redhat.com ([209.132.183.28]:7237)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1UDeYb-0001w5-QE
	for qemu-devel@nongnu.org; Thu, 07 Mar 2013 12:24:41 -0500
From: Markus Armbruster <armbru@redhat.com>
References: <20130307164812.GA29676@redhat.com>
Date: Thu, 07 Mar 2013 18:24:39 +0100
In-Reply-To: <20130307164812.GA29676@redhat.com> (Michael S. Tsirkin's message
	of "Thu, 7 Mar 2013 18:48:12 +0200")
Message-ID: <87r4jr2kdk.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Qemu-devel] [PATCHv3] qdev: DEVICE_DELETED event
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: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Anthony Liguori <aliguori@us.ibm.com>, Eduardo Habkost <ehabkost@redhat.com>, libvir-list@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>, Andreas =?utf-8?Q?F=C3=A4rber?= <afaerber@suse.de>

"Michael S. Tsirkin" <mst@redhat.com> writes:

> libvirt has a long-standing bug: when removing the device,
> it can request removal but does not know when the
> removal completes. Add an event so we can fix this in a robust way.

This is *v4*.  I think you should respin to avoid confusing Anthony's
tools.  Recommend to delay the respin until the discussion we're having
in the v1 thread has run its course.