From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Chunyan Liu <cyliu@suse.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [RESEND PATCH V3] qemu-img info: show nocow info
Date: Fri, 21 Nov 2014 09:29:52 -0700 [thread overview]
Message-ID: <546F6880.3080106@redhat.com> (raw)
In-Reply-To: <20141121162505.GF3956@noname.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]
On 11/21/2014 09:25 AM, Kevin Wolf wrote:
> Am 30.07.2014 um 04:55 hat Chunyan Liu geschrieben:
>> Add nocow info in 'qemu-img info' output to show whether the file
>> currently has NOCOW flag set or not.
>>
>> Signed-off-by: Chunyan Liu <cyliu@suse.com>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>> ---
>> Resend for QEMU 2.2. Change json version comment. Add Reviewed-by.
>>
>> block/qapi.c | 25 +++++++++++++++++++++++++
>> qapi/block-core.json | 5 ++++-
>> 2 files changed, 29 insertions(+), 1 deletion(-)
>
> Unfortunately, I have never been CCed on this patch and I saw the code
> it added only now. I think it doesn't work correctly and has the wrong
> design, so I would prefer to revert it for 2.2 rather than making a bad
> API stable.
Even though I reviewed the original, you make some valid points, and I
can agree to a revert to avoid baking in a mistake.
>> @@ -126,7 +128,8 @@
>> '*backing-filename': 'str', '*full-backing-filename': 'str',
>> '*backing-filename-format': 'str', '*snapshots': ['SnapshotInfo'],
>> '*backing-image': 'ImageInfo',
>> - '*format-specific': 'ImageInfoSpecific' } }
>> + '*format-specific': 'ImageInfoSpecific',
>> + '*nocow': 'bool' } }
>
> As this field makes only sense for raw-posix, it should be moved to
> ImageInfoSpecific. ("format-specific" is also an unfortunate misnomer,
> it should be "driver-specific", but it's too late to fix that.)
Yes, that alone is a compelling reason to back this out and get the
interface right.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-11-21 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 2:55 [Qemu-devel] [RESEND PATCH V3] qemu-img info: show nocow info Chunyan Liu
2014-07-30 15:00 ` Stefan Hajnoczi
2014-11-21 16:25 ` Kevin Wolf
2014-11-21 16:29 ` Eric Blake [this message]
2014-11-24 3:11 ` Chun Yan Liu
2014-11-24 9:34 ` Kevin Wolf
-- strict thread matches above, loose matches on Subject: below --
2014-07-29 7:18 Chunyan Liu
2014-07-29 12:45 ` Eric Blake
2014-07-30 2:57 ` Chun Yan Liu
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=546F6880.3080106@redhat.com \
--to=eblake@redhat.com \
--cc=cyliu@suse.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 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).