From: Eric Blake <eblake@redhat.com>
To: libguestfs@redhat.com
Cc: vsementsov@virtuozzo.com, QEMU <qemu-devel@nongnu.org>,
qemu-block@nongnu.org
Subject: Re: [Libguestfs] [libnbd PATCH] info: Add support for new 'qemu-nbd -A' qemu:allocation-depth
Date: Tue, 27 Oct 2020 10:33:48 -0500 [thread overview]
Message-ID: <e1b65875-c47b-4aea-98b3-599e06627ee6@redhat.com> (raw)
In-Reply-To: <20201016152318.80889-1-eblake@redhat.com>
On 10/16/20 10:23 AM, Eric Blake wrote:
> A rather trivial decoding; we may enhance it further if qemu extends
> things to give an integer depth alongside its tri-state encoding.
> ---
>
> I'll wait to push this to libnbd until the counterpart qemu patches
> land upstream, although it looks like I've got positive review.
Whoops, I accidentally pushed this before qemu stuff landed upstream,
and in the meantime, we changed our minds on what to expose over
qemu:allocation-depth to be a bare integer rather than a tri-state.
I'll push this followup (but this time, wait for the actual qemu patch
to land). In fact, I should probably add test-suite coverage...
From eba8734654e6fd340e18b3e07c3213ed1a0ab9e8 Mon Sep 17 00:00:00 2001
From: Eric Blake <eblake@redhat.com>
Date: Tue, 27 Oct 2020 10:27:25 -0500
Subject: [libnbd PATCH] info: Adjust to actual 'qemu-nbd -A' semantics
Review on the qemu list has led to an altered definition of what
'qemu:allocation-depth' should report: rather than a tri-state value,
it is an actual depth. It's time to match what actually got committed
into qemu, which in turn means a slight refactoring to use a malloc'd
string for a description.
Fixes: 71455c021
---
info/nbdinfo.c | 27 +++++++++++++++------------
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/info/nbdinfo.c b/info/nbdinfo.c
index 2b22f51..b152f28 100644
--- a/info/nbdinfo.c
+++ b/info/nbdinfo.c
@@ -767,28 +767,30 @@ get_content (struct nbd_handle *nbd, int64_t size)
}
/* Callback handling --map. */
-static const char *
+static char *
extent_description (const char *metacontext, uint32_t type)
{
+ char *ret;
+
if (strcmp (metacontext, "base:allocation") == 0) {
switch (type) {
- case 0: return "allocated";
- case 1: return "hole";
- case 2: return "zero";
- case 3: return "hole,zero";
+ case 0: return strdup ("allocated");
+ case 1: return strdup ("hole");
+ case 2: return strdup ("zero");
+ case 3: return strdup ("hole,zero");
}
}
else if (strncmp (metacontext, "qemu:dirty-bitmap:", 18) == 0) {
switch (type) {
- case 0: return "clean";
- case 1: return "dirty";
+ case 0: return strdup ("clean");
+ case 1: return strdup ("dirty");
}
}
else if (strcmp (metacontext, "qemu:allocation-depth") == 0) {
- switch (type & 3) {
- case 0: return "unallocated";
- case 1: return "local";
- case 2: return "backing";
+ switch (type) {
+ case 0: return strdup ("unallocated");
+ case 1: return strdup ("local");
+ case 2: asprintf (&ret, "backing depth %d", type); return ret;
}
}
@@ -810,7 +812,7 @@ extent_callback (void *user_data, const char
*metacontext,
/* Print the entries received. */
for (i = 0; i < nr_entries; i += 2) {
- const char *descr = extent_description (map, entries[i+1]);
+ char *descr = extent_description (map, entries[i+1]);
if (!json_output) {
fprintf (fp, "%10" PRIu64 " "
@@ -837,6 +839,7 @@ extent_callback (void *user_data, const char
*metacontext,
comma = true;
}
+ free (descr);
offset += entries[i];
}
--
2.29.0
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-10-27 15:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 21:55 [PATCH v4 0/7] Exposing backing-chain allocation over NBD Eric Blake
2020-10-09 21:55 ` [PATCH v4 1/7] nbd: Utilize QAPI_CLONE for type conversion Eric Blake
2020-10-14 11:15 ` Vladimir Sementsov-Ogievskiy
2020-10-23 16:15 ` Eric Blake
2020-10-09 21:55 ` [PATCH v4 2/7] nbd: Add new qemu:allocation-depth metadata context Eric Blake
2020-10-14 11:52 ` Vladimir Sementsov-Ogievskiy
2020-10-22 21:45 ` Eric Blake
2020-10-09 21:55 ` [PATCH v4 3/7] nbd: Add 'qemu-nbd -A' to expose allocation depth Eric Blake
2020-10-09 21:55 ` [PATCH v4 4/7] nbd: Update qapi to support exporting multiple bitmaps Eric Blake
2020-10-14 12:15 ` Vladimir Sementsov-Ogievskiy
2020-10-19 21:45 ` Eric Blake
2020-10-20 8:51 ` Markus Armbruster
2020-10-20 18:26 ` Eric Blake
2020-10-21 4:19 ` Markus Armbruster
2020-10-09 21:55 ` [PATCH v4 5/7] nbd: Simplify qemu bitmap context name Eric Blake
2020-10-14 12:21 ` Vladimir Sementsov-Ogievskiy
2020-10-09 21:55 ` [PATCH v4 6/7] nbd: Refactor counting of metadata contexts Eric Blake
2020-10-14 12:27 ` Vladimir Sementsov-Ogievskiy
2020-10-09 21:55 ` [PATCH v4 7/7] nbd: Allow export of multiple bitmaps for one device Eric Blake
2020-10-14 14:42 ` Vladimir Sementsov-Ogievskiy
2020-10-15 12:59 ` Eric Blake
[not found] ` <20201016152318.80889-1-eblake@redhat.com>
2020-10-27 15:33 ` Eric Blake [this message]
2020-10-27 19:40 ` [Libguestfs] [libnbd PATCH] info: Add support for new 'qemu-nbd -A' qemu:allocation-depth Richard W.M. Jones
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=e1b65875-c47b-4aea-98b3-599e06627ee6@redhat.com \
--to=eblake@redhat.com \
--cc=libguestfs@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 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).