qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, jcody@redhat.com,
	armbru@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 2/9] block: User BdrvChild callback for device name
Date: Wed, 27 Apr 2016 15:20:24 +0200	[thread overview]
Message-ID: <1461763231-17598-3-git-send-email-kwolf@redhat.com> (raw)
In-Reply-To: <1461763231-17598-1-git-send-email-kwolf@redhat.com>

In order to get rid of bs->blk for bdrv_get_device_name() and
bdrv_get_device_or_node_name(), ask all parents for their name and
simply pick the first one.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
---
 block.c                   | 22 ++++++++++++++++++++--
 block/block-backend.c     |  6 ++++++
 include/block/block_int.h |  5 +++++
 3 files changed, 31 insertions(+), 2 deletions(-)

diff --git a/block.c b/block.c
index 69ee791..a8df72f 100644
--- a/block.c
+++ b/block.c
@@ -2896,10 +2896,28 @@ const char *bdrv_get_node_name(const BlockDriverState *bs)
     return bs->node_name;
 }
 
+static const char *bdrv_get_parent_name(const BlockDriverState *bs)
+{
+    BdrvChild *c;
+    const char *name;
+
+    /* If multiple parents have a name, just pick the first one. */
+    QLIST_FOREACH(c, &bs->parents, next_parent) {
+        if (c->role->get_name) {
+            name = c->role->get_name(c);
+            if (name && *name) {
+                return name;
+            }
+        }
+    }
+
+    return NULL;
+}
+
 /* TODO check what callers really want: bs->node_name or blk_name() */
 const char *bdrv_get_device_name(const BlockDriverState *bs)
 {
-    return bs->blk ? blk_name(bs->blk) : "";
+    return bdrv_get_parent_name(bs) ?: "";
 }
 
 /* This can be used to identify nodes that might not have a device
@@ -2908,7 +2926,7 @@ const char *bdrv_get_device_name(const BlockDriverState *bs)
  * absent, then this returns an empty (non-null) string. */
 const char *bdrv_get_device_or_node_name(const BlockDriverState *bs)
 {
-    return bs->blk ? blk_name(bs->blk) : bs->node_name;
+    return bdrv_get_parent_name(bs) ?: bs->node_name;
 }
 
 int bdrv_get_flags(BlockDriverState *bs)
diff --git a/block/block-backend.c b/block/block-backend.c
index 7f507ba..34f747e 100644
--- a/block/block-backend.c
+++ b/block/block-backend.c
@@ -97,11 +97,17 @@ static void blk_root_drained_end(BdrvChild *child);
 static void blk_root_change_media(BdrvChild *child, bool load);
 static void blk_root_resize(BdrvChild *child);
 
+static const char *blk_root_get_name(BdrvChild *child)
+{
+    return blk_name(child->opaque);
+}
+
 static const BdrvChildRole child_root = {
     .inherit_options    = blk_root_inherit_options,
 
     .change_media       = blk_root_change_media,
     .resize             = blk_root_resize,
+    .get_name           = blk_root_get_name,
 
     .drained_begin      = blk_root_drained_begin,
     .drained_end        = blk_root_drained_end,
diff --git a/include/block/block_int.h b/include/block/block_int.h
index 9938a3d..f4a0941 100644
--- a/include/block/block_int.h
+++ b/include/block/block_int.h
@@ -365,6 +365,11 @@ struct BdrvChildRole {
     void (*change_media)(BdrvChild *child, bool load);
     void (*resize)(BdrvChild *child);
 
+    /* Returns a name that is supposedly more useful for human users than the
+     * node name for identifying the node in question (in particular, a BB
+     * name), or NULL if the parent can't provide a better name. */
+    const char* (*get_name)(BdrvChild *child);
+
     void (*drained_begin)(BdrvChild *child);
     void (*drained_end)(BdrvChild *child);
 };
-- 
1.8.3.1

  parent reply	other threads:[~2016-04-27 13:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 13:20 [Qemu-devel] [PATCH v2 0/9] block: Remove BlockDriverState.blk Kevin Wolf
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 1/9] block: Use BdrvChild callbacks for change_media/resize Kevin Wolf
2016-04-27 13:20 ` Kevin Wolf [this message]
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 3/9] blockjob: Don't set iostatus of target Kevin Wolf
2016-05-06 12:01   ` Max Reitz
2016-05-06 12:32     ` Max Reitz
2016-05-06 13:31       ` Kevin Wolf
2016-05-06 13:40         ` Max Reitz
2016-05-06 14:12           ` Kevin Wolf
2016-05-11 15:02             ` Max Reitz
2016-05-06 14:34         ` Eric Blake
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 4/9] blockjob: Don't touch BDS iostatus Kevin Wolf
2016-05-06 13:37   ` Max Reitz
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 5/9] block: Remove bdrv_aio_multiwrite() Kevin Wolf
2016-05-06 12:29   ` Eric Blake
2016-05-12 20:18   ` Eric Blake
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 6/9] block: Add bdrv_has_blk() Kevin Wolf
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 7/9] block: Avoid bs->blk in bdrv_next() Kevin Wolf
2016-05-06 12:54   ` Max Reitz
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 8/9] block: Don't return throttling info in query-named-block-nodes Kevin Wolf
2016-04-27 13:20 ` [Qemu-devel] [PATCH v2 9/9] block: Remove BlockDriverState.blk Kevin Wolf
2016-05-17 14:28 ` [Qemu-devel] [PATCH v2 0/9] " Kevin Wolf

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=1461763231-17598-3-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).