From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nom2O-0003D4-Ft for qemu-devel@nongnu.org; Mon, 08 Mar 2010 18:07:00 -0500 Received: from [199.232.76.173] (port=50235 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nom2O-0003A2-2t for qemu-devel@nongnu.org; Mon, 08 Mar 2010 18:07:00 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NolwP-0002Qa-DC for qemu-devel@nongnu.org; Mon, 08 Mar 2010 18:00:50 -0500 Received: from mail2.shareable.org ([80.68.89.115]:44798) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NolwE-0002O0-7f for qemu-devel@nongnu.org; Mon, 08 Mar 2010 18:00:49 -0500 Date: Mon, 8 Mar 2010 23:00:22 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: bs->enable_write_cache and the guest ABI Message-ID: <20100308230022.GC16057@shareable.org> References: <4B93BB4A.8090605@redhat.com> <4B94D60A.7070006@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B94D60A.7070006@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Christoph Hellwig , qemu-devel , Juan Quintela Avi Kivity wrote: > I think we have to go with a qdev property as Christoph suggests. Then > it becomes the management's responsibility to set it right. How can the management be expected to know or follow dynamically changing guest state? There guests which disable a drive's write cache in some application scripts, and others which enable it in boot scripts. That's not something management should be knowing about. -- Jamie