From: Alberto Garcia <berto@igalia.com>
To: Eric Blake <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] block: allow BLOCK_IMAGE_CORRUPTED to have a node name
Date: Thu, 19 Mar 2015 23:38:40 +0100 [thread overview]
Message-ID: <20150319223840.GA13196@igalia.com> (raw)
In-Reply-To: <550B4A95.9060501@redhat.com>
On Thu, Mar 19, 2015 at 04:15:49PM -0600, Eric Blake wrote:
> >>> -# @device: device name
> >>> +# @device: device name, or node name if not present
> >>
> >> 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?
>
> How hard is it to output both 'device' and 'node' in the same event,
> if both are available?
It's a trivial change, there's no problem at all. I assume that, for
compatibility reasons, 'device' would continue to be present even if
it's empty, but would you prefer to have 'node-name' as an optional
field?
> And for this particular event, which is not tied to block jobs but
> to generic block operation, isn't it possible that we could be
> reporting a corrupted backing chain where we have neither a device
> name (it is not the active layer) nor a node name (if we don't add
> Jeff's patch to auto-name all nodes)? In such a case, I don't know
> that we can do much better anyways.
Yes, it is perfectly possible. I guess any software that wants to
handle those scenarios probably wants to give names to all nodes.
From the QEMU side, apart from giving automatic names to all nodes I
don't see any other solution.
Berto
next prev parent reply other threads:[~2015-03-19 22:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 15:43 [Qemu-devel] [PATCH 0/3] Add bdrv_get_device_or_node_name() Alberto Garcia
2015-03-19 15:43 ` [Qemu-devel] [PATCH 1/3] block: add bdrv_get_device_or_node_name() Alberto Garcia
2015-03-19 19:26 ` Max Reitz
2015-03-20 7:40 ` Markus Armbruster
2015-03-20 8:03 ` Alberto Garcia
2015-03-20 8:47 ` Markus Armbruster
2015-03-19 15:43 ` [Qemu-devel] [PATCH 2/3] block: use bdrv_get_device_or_node_name() in error messages Alberto Garcia
2015-03-19 19:37 ` Max Reitz
2015-03-20 7:52 ` Markus Armbruster
2015-03-19 15:43 ` [Qemu-devel] [PATCH 3/3] block: allow BLOCK_IMAGE_CORRUPTED to have a node name Alberto Garcia
2015-03-19 19:42 ` Max Reitz
2015-03-19 21:42 ` Alberto Garcia
2015-03-19 21:52 ` Max Reitz
2015-03-19 22:04 ` Alberto Garcia
2015-03-19 22:15 ` Eric Blake
2015-03-19 22:38 ` Alberto Garcia [this message]
2015-03-19 23:14 ` Eric Blake
2015-03-20 9:23 ` Alberto Garcia
2015-03-19 19:37 ` [Qemu-devel] [PATCH 0/3] Add bdrv_get_device_or_node_name() Max Reitz
2015-03-19 21:49 ` Alberto Garcia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150319223840.GA13196@igalia.com \
--to=berto@igalia.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.