From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57370) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYiCe-0007sa-M3 for qemu-devel@nongnu.org; Thu, 19 Mar 2015 17:42:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YYiCa-0007By-Ja for qemu-devel@nongnu.org; Thu, 19 Mar 2015 17:42:08 -0400 Received: from smtp3.mundo-r.com ([212.51.32.191]:14518 helo=smtp4.mundo-r.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYiCa-0007Bn-Cw for qemu-devel@nongnu.org; Thu, 19 Mar 2015 17:42:04 -0400 Date: Thu, 19 Mar 2015 22:42:01 +0100 From: Alberto Garcia Message-ID: <20150319214201.GA11212@igalia.com> References: <9d3f0e0ee6fcfc6300e165f79b46a4af0ffdc37d.1426779661.git.berto@igalia.com> <550B26AB.4050806@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <550B26AB.4050806@redhat.com> Subject: Re: [Qemu-devel] [PATCH 3/3] block: allow BLOCK_IMAGE_CORRUPTED to have a node name List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: Kevin Wolf , qemu-devel@nongnu.org, Stefan Hajnoczi (I forgot to Cc Eric in this series, doing it now) On Thu, Mar 19, 2015 at 03:42:35PM -0400, Max Reitz wrote: > > # Emitted when a corruption has been detected in a disk image > > # > >-# @device: device name > >+# @device: device name, or node name if not present > > Normally, if a field in QMP is designed @device, it contains a > device name. We do have combined device/node name fields, though (as > of John's incremental backup series, at least), but those are named > @node (which I proposed for patch 2, too). > > But renaming the field here will lead to breaking backwards > compatibility. I think just adding a @node-name field and keeping > @device as it is should be good enough here. I was doing the same that we discussed for BlockJobInfo here, where option b) seemed to have a bit more support: https://lists.gnu.org/archive/html/qemu-devel/2015-03/msg03651.html But yeah I personally don't mind extending the event with a new field. Would we make 'device' optional in this case? Berto