From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58419) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMGiI-0005e4-JY for qemu-devel@nongnu.org; Tue, 17 May 2011 05:37:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QMGiH-000736-NR for qemu-devel@nongnu.org; Tue, 17 May 2011 05:37:14 -0400 Received: from e28smtp02.in.ibm.com ([122.248.162.2]:37004) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QMGiH-000722-4b for qemu-devel@nongnu.org; Tue, 17 May 2011 05:37:13 -0400 Received: from d28relay05.in.ibm.com (d28relay05.in.ibm.com [9.184.220.62]) by e28smtp02.in.ibm.com (8.14.4/8.13.1) with ESMTP id p4H9b8tS012418 for ; Tue, 17 May 2011 15:07:08 +0530 Received: from d28av01.in.ibm.com (d28av01.in.ibm.com [9.184.220.63]) by d28relay05.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p4H9b70g3068052 for ; Tue, 17 May 2011 15:07:08 +0530 Received: from d28av01.in.ibm.com (loopback [127.0.0.1]) by d28av01.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p4H9b7Ik012911 for ; Tue, 17 May 2011 15:07:07 +0530 Message-ID: <4DD23D5F.9010508@in.ibm.com> Date: Tue, 17 May 2011 14:48:23 +0530 From: supriya kannery MIME-Version: 1.0 References: <20110516181023.7142.33402.sendpatchset@skannery> <20110516202354.GA8955@lst.de> In-Reply-To: <20110516202354.GA8955@lst.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC Patch 0/3]Qemu: Enable dynamic cache change through qemu monitor List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: Kevin Wolf , Supriya Kannery , qemu-devel@nongnu.org, Prerna Saxena Christoph Hellwig wrote: > Why are you even trying this again? Enabling control of cache setting from qemu monitor will help users/admins to accomplish cache value change without depending on the guest. > As explained very clearly last time you > can't change from a writeback-style to a write-through style I/O from > the monitor without creating massive data integrity problems. See my > patchset that allows changing this from the guest for how it should be > done - I just need to get back and revisit the virtio protocol support > for it. > > > ok, sure, I will go through your related patches and work further on this.