From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=36801 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PzRpq-00081H-9O for qemu-devel@nongnu.org; Tue, 15 Mar 2011 06:50:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PzRpp-00063J-Af for qemu-devel@nongnu.org; Tue, 15 Mar 2011 06:50:42 -0400 Received: from verein.lst.de ([213.95.11.211]:48457 helo=newverein.lst.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PzRpp-00060C-5t for qemu-devel@nongnu.org; Tue, 15 Mar 2011 06:50:41 -0400 Date: Tue, 15 Mar 2011 11:50:40 +0100 From: Christoph Hellwig Message-ID: <20110315105040.GA25001@lst.de> References: <20110314171627.GB1062@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: [Qemu-devel] Re: Write cache enable from guest at runtime List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Kevin Wolf , Anthony Liguori , qemu-devel , Christoph Hellwig , Prerna Saxena On Mon, Mar 14, 2011 at 07:15:14PM +0000, Stefan Hajnoczi wrote: > Sounds like a good idea. Feel free to post the patches RFC and I or > someone else can debug and polish them if you don't have time. By looking at your document and doing what you recommend against I think I got a much simpler solution than what I had before. I didn't know we could actually write to the config space. The vpcu synchronous behaviour is not a problem as it's done seldomly, and we can trivially check against errors by reading the value back. I've just started building this variant, and it seems surprisingly simple.