From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:44923)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1V2kq5-00030D-Vy
	for qemu-devel@nongnu.org; Fri, 26 Jul 2013 12:25:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1V2kq5-0006yr-2P
	for qemu-devel@nongnu.org; Fri, 26 Jul 2013 12:25:57 -0400
Received: from mx1.redhat.com ([209.132.183.28]:61685)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1V2kq4-0006yn-QY
	for qemu-devel@nongnu.org; Fri, 26 Jul 2013 12:25:57 -0400
Message-ID: <51F2A2EE.5040403@redhat.com>
Date: Fri, 26 Jul 2013 18:25:18 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1374765505-14356-1-git-send-email-stefanha@redhat.com>
	<1374765505-14356-7-git-send-email-stefanha@redhat.com>
	<20130726161001.GA28317@localhost.localdomain>
In-Reply-To: <20130726161001.GA28317@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v6 06/18] aio: stop using .io_flush()
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: Jeff Cody <jcody@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Ping Fan Liu <pingfank@linux.vnet.ibm.com>, Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org, Michael Roth <mdroth@linux.vnet.ibm.com>, alex@alex.org.uk

Il 26/07/2013 18:10, Jeff Cody ha scritto:
> +   /* wait until next event that is not aio_notify() */
> +   while (count > 1) {
> 
> This would assume of course that aio_notify() is always first in the
> list.

No, you cannot assume that.  Any bdrv can be opened early (with -drive)
and then associated to an AioContext that is created later (when the
dataplane thread start).

Paolo