From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KTOtH-00038w-Qi
	for qemu-devel@nongnu.org; Wed, 13 Aug 2008 18:32:27 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KTOtG-00038C-E1
	for qemu-devel@nongnu.org; Wed, 13 Aug 2008 18:32:27 -0400
Received: from [199.232.76.173] (port=33361 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KTOtG-000388-3X
	for qemu-devel@nongnu.org; Wed, 13 Aug 2008 18:32:26 -0400
Received: from mtaout01-winn.ispmail.ntl.com ([81.103.221.47]:45100)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <samuel.thibault@labri.fr>) id 1KTOtF-0003MX-QS
	for qemu-devel@nongnu.org; Wed, 13 Aug 2008 18:32:26 -0400
Received: from aamtaout04-winn.ispmail.ntl.com ([81.103.221.35])
	by mtaout01-winn.ispmail.ntl.com with ESMTP id
	<20080813223224.GLQV777.mtaout01-winn.ispmail.ntl.com@aamtaout04-winn.ispmail.ntl.com>
	for <qemu-devel@nongnu.org>; Wed, 13 Aug 2008 23:32:24 +0100
Received: from implementation.famille.thibault.fr ([82.21.96.230])
	by aamtaout04-winn.ispmail.ntl.com with ESMTP id
	<20080813223224.SIDD18637.aamtaout04-winn.ispmail.ntl.com@implementation.famille.thibault.fr>
	for <qemu-devel@nongnu.org>; Wed, 13 Aug 2008 23:32:24 +0100
Received: from samy by implementation.famille.thibault.fr with local (Exim
	4.69) (envelope-from <samuel.thibault@labri.fr>) id 1KTOtE-0002La-Tj
	for qemu-devel@nongnu.org; Thu, 14 Aug 2008 00:32:24 +0200
Date: Wed, 13 Aug 2008 23:32:24 +0100
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] [PATCH] Flush pending AIO on reboot and shutdown.
Message-ID: <20080813223224.GG4766@implementation>
References: <20080813132358.17672.68212.stgit@gleb-debian.qumranet.com.qumranet.com>
	<48A2E732.4040501@codemonkey.ws>
	<20080813141346.GC17567@minantech.com>
	<48A2F89A.20609@codemonkey.ws>
	<20080813152329.GG17567@minantech.com>
	<48A30395.6060706@codemonkey.ws>
	<20080813183544.GA29998@minantech.com>
	<48A32FF1.5040302@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <48A32FF1.5040302@codemonkey.ws>
Reply-To: qemu-devel@nongnu.org
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

Anthony Liguori, le Wed 13 Aug 2008 14:03:13 -0500, a écrit :
> From the guest's perspective, data is only written to disk after a
> write completion has be issued.  I think it's worse for data to end up
> being written to disk without that completion ever being seen by the
> guest.

Well, the guest is notified asynchronously with real hardware, so it may
miss a completion too.

Samuel