From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: libvir-list@redhat.com, Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] qapi: add dirty-bitmaps to query-named-block-nodes result
Date: Wed, 17 Jul 2019 15:05:02 -0500 [thread overview]
Message-ID: <8ac42074-4a65-089a-3bf9-07cacda284ce@redhat.com> (raw)
In-Reply-To: <c2bbf3a0-c7f0-263c-a191-ebe54c784349@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1018 bytes --]
On 7/17/19 2:21 PM, John Snow wrote:
>>
>> Is this worth squeezing into 4.1, to start the deprecation clock one
>> cycle earlier (on the grounds that the missing information for anonymous
>> nodes is a bug)? Or am I pushing the boundaries too far, where keeping
>> this as 4.2 material remains the best course of action?
>>
>
> Appealing option. If you think the deprecation plan is actionable enough
> for libvirt, I'm in favor.
I know my code for scraping query-block output during
virDomainCheckpointGetXMLDesc(,VIR_DOMAIN_CHECKPOINT_XML_SIZE) that
reports the size of the bitmap to the end user hasn't landed yet, and
that appears to be the only client in libvirt of this information at the
moment; but it's not a problem for me to check introspection for where
to find it (as libvirt already has a good framework for scraping
introspection for other reasons).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-17 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 17:39 [Qemu-devel] [PATCH v3] qapi: add dirty-bitmaps to query-named-block-nodes result John Snow
2019-07-17 17:47 ` John Snow
2019-07-17 19:13 ` Eric Blake
2019-07-17 19:21 ` John Snow
2019-07-17 20:05 ` Eric Blake [this message]
2019-07-17 20:32 ` John Snow
2019-07-17 21:12 ` John Snow
2019-07-18 10:20 ` [Qemu-devel] [libvirt] " no-reply
2019-07-18 17:32 ` John Snow
2019-07-24 4:47 ` [Qemu-devel] " Markus Armbruster
2019-07-24 22:06 ` John Snow
2019-07-25 6:06 ` Markus Armbruster
2019-07-25 16:13 ` John Snow
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=8ac42074-4a65-089a-3bf9-07cacda284ce@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@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 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.