From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:60229) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TBQgB-0001YT-Q8 for qemu-devel@nongnu.org; Tue, 11 Sep 2012 09:39:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TBQg6-0002hI-Rf for qemu-devel@nongnu.org; Tue, 11 Sep 2012 09:39:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45166) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TBQg6-0002hB-HY for qemu-devel@nongnu.org; Tue, 11 Sep 2012 09:38:58 -0400 Message-ID: <504F3ED9.6060505@redhat.com> Date: Tue, 11 Sep 2012 15:38:33 +0200 From: Kevin Wolf MIME-Version: 1.0 References: <1343127865-16608-1-git-send-email-pbonzini@redhat.com> <1343127865-16608-23-git-send-email-pbonzini@redhat.com> In-Reply-To: <1343127865-16608-23-git-send-email-pbonzini@redhat.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 22/47] block: make device optional in BlockInfo List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: jcody@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com Am 24.07.2012 13:04, schrieb Paolo Bonzini: > Targets of a mirroring operation will not have a device. Once we have > -blockdev or equivalent, "detached" block devices and non-anonymous > backing files also will not have a device. > > Signed-off-by: Paolo Bonzini > --- > qapi-schema.json | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/qapi-schema.json b/qapi-schema.json > index fca1806..b00d8c6 100644 > --- a/qapi-schema.json > +++ b/qapi-schema.json > @@ -443,7 +443,8 @@ > # Block device information. This structure describes a virtual device and > # the backing device associated with it. > # > -# @device: The device name associated with the virtual device. > +# @device: #optional The device name associated with the virtual device. > +# Always included in the output of query-block. > # > # @type: This field is returned only for compatibility reasons, it should > # not be used (always returns 'unknown') > @@ -465,7 +466,7 @@ > # Since: 0.14.0 > ## > { 'type': 'BlockInfo', > - 'data': {'device': 'str', 'type': 'str', 'removable': 'bool', > + 'data': {'*device': 'str', 'type': 'str', 'removable': 'bool', > 'locked': 'bool', '*inserted': 'BlockDeviceInfo', > '*tray_open': 'bool', '*io-status': 'BlockDeviceIoStatus'} } Is this really a compatible change? That 'device' is basically the unique key by which block device are identified doesn't exactly make feel more comfortable about the change. Of course, not making it optional means that basically we need to go the way of referencing the block device in query-block-jobs immediately instead of thinking about it later. You know that I preferred this from the start, and this change is just another detail that makes me think it's the right thing to do. Kevin