From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=55407 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pu58h-0006Yq-35 for qemu-devel@nongnu.org; Mon, 28 Feb 2011 10:36:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pu58g-0004CS-6u for qemu-devel@nongnu.org; Mon, 28 Feb 2011 10:35:59 -0500 Received: from mail-gy0-f173.google.com ([209.85.160.173]:60470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pu58g-0004CL-3P for qemu-devel@nongnu.org; Mon, 28 Feb 2011 10:35:58 -0500 Received: by gyd8 with SMTP id 8so1920010gyd.4 for ; Mon, 28 Feb 2011 07:35:57 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4D6BBB72.6040205@redhat.com> References: <20110228171956.05a84fb9@zephyr> <4D6BBB72.6040205@redhat.com> Date: Mon, 28 Feb 2011 15:35:56 +0000 Message-ID: Subject: Re: [Qemu-devel] [RFC][PATCH 0/2] Allow cache settings for block devices to be changed at runtime. From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: Anthony Liguori , Stefan Hajnoczi , qemu-devel , Ananth Narayan , Prerna Saxena , Christoph Hellwig On Mon, Feb 28, 2011 at 3:12 PM, Kevin Wolf wrote: > Am 28.02.2011 12:49, schrieb Prerna Saxena: >> The following patchset introduces monitor commands: >> >> 1. set_cache DEVICE CACHE-SETTING >> Change cache settings for block device, DEVICE, through the monitor. >> (Available options : 'none', 'writeback', 'writethrough') >> Eg, >> (qemu)set_cache ide0-hd0 none >> -> Changes cache setting for ide0-hd0 to 'none' > > Not sure if adding this interface is a good idea. I see that you only > add it for HMP, and we may consider that, but it's definitely not > suitable for QMP. > > One reason is that none/writethrough/writeback/unsafe isn't really what > we want to use long term. We want to separate advertising a write cache > (which is guest visible) from things like whether to use O_DIRECT or not. > > In the past, Christoph mentioned that he had patches to make these > separate and even let the guest change the "write cache enabled" flag, > which would probably solve most of the use cases of this patch. Toggling host page cache at runtime is useful too because it saves having to restart VMs. I agree that the guest should control the emulated drive cache at runtime and we probably don't want to allow toggling that from the host - it could be dangerous :). Stefan