From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KTLTa-0004rA-0E for qemu-devel@nongnu.org; Wed, 13 Aug 2008 14:53:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KTLTZ-0004qt-B7 for qemu-devel@nongnu.org; Wed, 13 Aug 2008 14:53:41 -0400 Received: from [199.232.76.173] (port=56791 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KTLTZ-0004qq-9B for qemu-devel@nongnu.org; Wed, 13 Aug 2008 14:53:41 -0400 Received: from il.qumranet.com ([212.179.150.194]:39112) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KTLTY-0006rW-Pu for qemu-devel@nongnu.org; Wed, 13 Aug 2008 14:53:41 -0400 Received: from gleb-debian.qumranet.com (gleb-debian.qumranet.com.qumranet.com [172.16.15.143]) by il.qumranet.com (Postfix) with ESMTP id AC1ED250310 for ; Wed, 13 Aug 2008 21:53:39 +0300 (IDT) Date: Wed, 13 Aug 2008 21:53:39 +0300 From: Gleb Natapov Subject: Re: [Qemu-devel] [PATCH] Flush pending AIO on reboot and shutdown. Message-ID: <20080813185339.GB29998@minantech.com> 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> <48A32AA2.6030902@qumranet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48A32AA2.6030902@qumranet.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Wed, Aug 13, 2008 at 09:40:34PM +0300, Avi Kivity wrote: > Gleb Natapov wrote: >> but what bother me is that we >> consciously drop user data that we can easily save. Why? Real HW tries >> hard to save every bit of user data and we just decided to drop it. The >> difference between cancel or complete a request may be corrupted or not >> corrupted file system after a crash. >> >> > > If a guest didn't wait for an I/O to complete, it shouldn't expect it to > be on disk. If you'll save your swiss bank account details in file and suddenly your guest will crash, you'll surely appreciate if qemu will save it for you :) > > Of course, we can have the IDE layer wait instead of cancelling, which > will get the request onto the disk. > That is the current approach, but the wait is done for all block IO not just IDE. -- Gleb.