qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Ian Main <imain@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V4 4/4] Change default to qcow2 for sync mode none.
Date: Thu, 18 Jul 2013 11:32:52 -0600	[thread overview]
Message-ID: <51E826C4.6090300@redhat.com> (raw)
In-Reply-To: <51E82579.20201@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

On 07/18/2013 11:27 AM, Eric Blake wrote:

>>      if (!has_format) {
>> -        format = mode == NEW_IMAGE_MODE_EXISTING ? NULL : bs->drv->format_name;
>> +        format = mode == NEW_IMAGE_MODE_EXISTING ? NULL : "qcow2";
> 
> Is this the right thing to do?  Or should we do:
> 
> if (!has_format) {
>     if (mode == NEW_IMAGE_MODE_EXISTING) {
>         format = NULL;
>     } else {
>         format = bs->drv->format_name ?: "qcow2";
>     }
> }
> 
> That is, I think we should default to doing a backup in the format given
> by the original (what if the original is qed, which also supports
> backing files), and only use qcow2 when there is no guidance whatsoever.
> 
> But in practice, I don't care

Well, I _DO_ care about one thing - make sure that the qapi-schema.json
page accurately documents how this variable is defaulted for callers
that don't care about the implications of omitting a format.

Or we could simplify life by making 'format' mandatory for drive-backup;
it was optional for 'drive-mirror' due to incremental implementation,
but for 'drive-backup', we still have the opportunity to do things right
from the first release.

-- 
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: 621 bytes --]

  reply	other threads:[~2013-07-18 17:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 20:04 [Qemu-devel] [PATCH V4 0/4] Implement sync modes for drive-backup Ian Main
2013-07-17 20:04 ` [Qemu-devel] [PATCH V4 1/4] " Ian Main
2013-07-18 17:19   ` Eric Blake
2013-07-18 19:06     ` Ian Main
2013-07-18 19:54       ` Eric Blake
2013-07-19 21:56         ` Ian Main
2013-07-17 20:04 ` [Qemu-devel] [PATCH V4 2/4] Add tests for sync modes 'TOP' and 'NONE' Ian Main
2013-07-17 20:04 ` [Qemu-devel] [PATCH V4 3/4] Add backing drive while performing backup Ian Main
2013-07-18  6:39   ` Fam Zheng
2013-07-18 13:13     ` Paolo Bonzini
2013-07-19  1:13       ` Fam Zheng
2013-07-19 20:15         ` Paolo Bonzini
2013-07-17 20:04 ` [Qemu-devel] [PATCH V4 4/4] Change default to qcow2 for sync mode none Ian Main
2013-07-18 17:27   ` Eric Blake
2013-07-18 17:32     ` Eric Blake [this message]
2013-07-18 18:03       ` Ian Main
2013-07-18 18:48         ` Eric Blake
2013-07-18 18:06     ` Ian Main
  -- strict thread matches above, loose matches on Subject: below --
2013-07-18 18:47 Ian Main
2013-07-18 18:56 ` Eric Blake
2013-07-18 19:13   ` Ian Main
2013-07-18 19:55     ` Eric Blake

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=51E826C4.6090300@redhat.com \
    --to=eblake@redhat.com \
    --cc=imain@redhat.com \
    --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).