qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/11] block: Use BB function in .bdrv_create() implementations
Date: Mon, 14 Mar 2016 18:34:31 +0100	[thread overview]
Message-ID: <20160314173431.GC4812@noname.redhat.com> (raw)
In-Reply-To: <56E6ED01.3080800@redhat.com>

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

Am 14.03.2016 um 17:55 hat Max Reitz geschrieben:
> On 14.03.2016 12:31, Kevin Wolf wrote:
> > Am 08.03.2016 um 17:34 hat Kevin Wolf geschrieben:
> >> All users of the block layers are supposed to go through a BlockBackend.
> >> The .bdrv_create() implementations are such users, so this series
> >> converts them.
> >>
> >> This series (specifically patch 1) will also help with moving the
> >> writethrough cache implementation from BDS to BB, where it really
> >> belongs. Once this is moved, it wouldn't be possible to use bdrv_open()
> >> to use a standalone BDS writethrough any more.
> >>
> >> Of course, writethrough doesn't make any sense in .bdrv_create() anyway,
> >> so while I'm still converting everything to BB where it would keep
> >> working (because that's the Right Thing), the drivers don't actually
> >> make use of this fact any more after this series.
> > 
> > Applied to the block branch.
> 
> Now you can't name any BB "image" any more if you want to use e.g.
> drive-mirror. Intended?

Not really. :-/

Of course, you're supposed to use blockdev-mirror anyway (does it even
exist?), but we should avoid that. Fortunately, your "Further BB work"
will tie the name to a monitor reference and BBs without a name become
valid then, I think.

So this might be a good excuse for getting that series into 2.6. :-)

Kevin

> Example:
> 
> $ x86_64-softmmu/qemu-system-x86_64 -drive
> if=none,id=image,file=null-co://,driver=raw -qmp stdio
> {'execute':'qmp_capabilities'}
> {"return": {}}
> {'execute':'drive-mirror','arguments':{'device':'image','target':'foo.qcow2','sync':'full','format':'qcow2'}}
> Formatting 'foo.qcow2', fmt=qcow2 size=1073741824 encryption=off
> cluster_size=65536 lazy_refcounts=off refcount_bits=16
> {"error": {"class": "GenericError", "desc": "Device with id 'image'
> already exists"}}
> 
> Max
> 




[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2016-03-14 17:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 16:34 [Qemu-devel] [PATCH 00/11] block: Use BB function in .bdrv_create() implementations Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 01/11] block: Use writeback " Kevin Wolf
2016-03-09 12:14   ` Paolo Bonzini
2016-03-09 12:27     ` Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 02/11] block: Introduce blk_set_allow_write_beyond_eof() Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 03/11] parallels: Use BB functions in .bdrv_create() Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 04/11] qcow: " Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 05/11] qcow2: " Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 06/11] qed: " Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 07/11] sheepdog: " Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 08/11] vdi: " Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 09/11] vhdx: " Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 10/11] vmdk: " Kevin Wolf
2016-03-08 16:34 ` [Qemu-devel] [PATCH 11/11] vpc: " Kevin Wolf
2016-03-14 11:31 ` [Qemu-devel] [PATCH 00/11] block: Use BB function in .bdrv_create() implementations Kevin Wolf
2016-03-14 16:55   ` Max Reitz
2016-03-14 17:34     ` Kevin Wolf [this message]

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=20160314173431.GC4812@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=mreitz@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).