From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v5 4/6] qemu-img: Use bdrv_filename() for map
Date: Mon, 19 Oct 2015 20:49:04 +0200 [thread overview]
Message-ID: <1445280546-26226-5-git-send-email-mreitz@redhat.com> (raw)
In-Reply-To: <1445280546-26226-1-git-send-email-mreitz@redhat.com>
Replaces bs->filename by the result of bdrv_filename() in the
qemu-img map subcommand. Since that value is queried relatively often,
however, it should be cached.
Signed-off-by: Max Reitz <mreitz@redhat.com>
---
qemu-img.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/qemu-img.c b/qemu-img.c
index 3025776..a44c77a 100644
--- a/qemu-img.c
+++ b/qemu-img.c
@@ -2142,6 +2142,7 @@ typedef struct MapEntry {
int64_t length;
int64_t offset;
BlockDriverState *bs;
+ char *bs_filename;
} MapEntry;
static void dump_map_entry(OutputFormat output_format, MapEntry *e,
@@ -2156,7 +2157,7 @@ static void dump_map_entry(OutputFormat output_format, MapEntry *e,
}
if ((e->flags & (BDRV_BLOCK_DATA|BDRV_BLOCK_ZERO)) == BDRV_BLOCK_DATA) {
printf("%#-16"PRIx64"%#-16"PRIx64"%#-16"PRIx64"%s\n",
- e->start, e->length, e->offset, e->bs->filename);
+ e->start, e->length, e->offset, e->bs_filename);
}
/* This format ignores the distinction between 0, ZERO and ZERO|DATA.
* Modify the flags here to allow more coalescing.
@@ -2306,6 +2307,12 @@ static int img_map(int argc, char **argv)
goto out;
}
+ if (next.bs == curr.bs) {
+ next.bs_filename = curr.bs_filename;
+ } else {
+ next.bs_filename = bdrv_filename(next.bs, NULL, 0);
+ }
+
if (curr.length != 0 && curr.flags == next.flags &&
curr.depth == next.depth &&
((curr.flags & BDRV_BLOCK_OFFSET_VALID) == 0 ||
@@ -2317,10 +2324,15 @@ static int img_map(int argc, char **argv)
if (curr.length > 0) {
dump_map_entry(output_format, &curr, &next);
}
+
+ if (curr.bs != next.bs) {
+ g_free(curr.bs_filename);
+ }
curr = next;
}
dump_map_entry(output_format, &curr, NULL);
+ g_free(curr.bs_filename);
out:
blk_unref(blk);
--
2.6.1
next prev parent reply other threads:[~2015-10-19 18:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 18:49 [Qemu-devel] [PATCH v5 0/6] block: Drop BDS.filename Max Reitz
2015-10-19 18:49 ` [Qemu-devel] [PATCH v5 1/6] block: Change bdrv_get_encrypted_filename() Max Reitz
2015-10-19 20:15 ` Eric Blake
2015-10-26 18:20 ` Kevin Wolf
2015-10-19 18:49 ` [Qemu-devel] [PATCH v5 2/6] block: Avoid BlockDriverState.filename Max Reitz
2015-10-19 20:35 ` Eric Blake
2015-10-26 16:51 ` Kevin Wolf
2015-10-19 18:49 ` [Qemu-devel] [PATCH v5 3/6] block: Add bdrv_filename() Max Reitz
2015-10-19 20:52 ` Eric Blake
2015-10-26 18:20 ` Kevin Wolf
2015-10-19 18:49 ` Max Reitz [this message]
2015-10-19 21:02 ` [Qemu-devel] [PATCH v5 4/6] qemu-img: Use bdrv_filename() for map Eric Blake
2015-10-26 18:21 ` Kevin Wolf
2015-10-19 18:49 ` [Qemu-devel] [PATCH v5 5/6] block: Drop BlockDriverState.filename Max Reitz
2015-10-19 21:11 ` Eric Blake
2015-10-27 9:39 ` Kevin Wolf
2015-10-19 18:49 ` [Qemu-devel] [PATCH v5 6/6] iotests: Test changed Quorum filename Max Reitz
2015-10-19 21:13 ` Eric Blake
2015-10-27 9:41 ` 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=1445280546-26226-5-git-send-email-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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).