From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39489) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QotLU-0000a2-6B for qemu-devel@nongnu.org; Thu, 04 Aug 2011 04:32:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QotLT-0007bL-4R for qemu-devel@nongnu.org; Thu, 04 Aug 2011 04:32:00 -0400 Received: from mail-gx0-f173.google.com ([209.85.161.173]:49052) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QotLS-0007bH-VV for qemu-devel@nongnu.org; Thu, 04 Aug 2011 04:31:59 -0400 Received: by gxk26 with SMTP id 26so1084605gxk.4 for ; Thu, 04 Aug 2011 01:31:58 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4E3A590B.1080609@linux.vnet.ibm.com> References: <20110727113000.25109.16204.sendpatchset@skannery> <20110727113045.25109.54866.sendpatchset@skannery> <4E300B8E.2020509@codemonkey.ws> <4E3036AA.8030604@codemonkey.ws> <4E36C608.2030107@codemonkey.ws> <4E36C9D3.4020803@redhat.com> <4E36C9F4.2080202@codemonkey.ws> <4E3A590B.1080609@linux.vnet.ibm.com> Date: Thu, 4 Aug 2011 09:31:57 +0100 Message-ID: From: Stefan Hajnoczi Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] [V5 Patch 3/4]Qemu: Command "block_set" for dynamic block params change List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: supriyak@linux.vnet.ibm.com Cc: Kevin Wolf , Christoph Hellwig , qemu-devel@nongnu.org On Thu, Aug 4, 2011 at 9:32 AM, Supriya Kannery wrote: > On 08/01/2011 09:14 PM, Anthony Liguori wrote: >> >> On 08/01/2011 10:44 AM, Kevin Wolf wrote: >>> >>> Am 01.08.2011 17:28, schrieb Anthony Liguori: >>>>> >>>>> 2. Top-level command for each parameter (e.g. block_set_hostcache). >>>>> Supported parameters are easily discoverable via query-commands. If >>>>> individual block devices support different sets of parameters then >>>>> they may have to return -ENOTSUPP. >>>>> >>>>> I like the block_set approach. >>>>> >>>>> Anthony, Kevin, Supriya: Any thoughts? >>>> >>>> For the sake of overall QMP sanity, I think block_set_hostcache is >>>> really our only option. >>> >>> Ideally we should have blockdev_add, and blockdev_set would just take >>> the same arguments and update the given driver. >> >> Ideally we'd have a backend_add, backend_set, etc. >> >> But in the absence of that, we should provide the best interface we can >> with the current tools we have. >> >> For now, using high level commands is the best we can do. > > Will be modifying code to have 'block_set_hostcache' command implemented. > Along with that, planning to implement 'query-block_set_hostcache', that > returns current hostcache setting > for all the applicable block devices. I don't think a query command is necessary since query-block already reports this information. Stefan