qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: kwolf@redhat.com, sw@weilnetz.de, qemu-devel@nongnu.org,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 2/5] block: vdi - use block layer ops in vdi_create, instead of posix calls
Date: Tue, 22 Jul 2014 16:19:24 -0400	[thread overview]
Message-ID: <20140722201924.GA31882@localhost.localdomain> (raw)
In-Reply-To: <53CEC642.6020804@redhat.com>

On Tue, Jul 22, 2014 at 10:14:58PM +0200, Max Reitz wrote:
> On 21.07.2014 21:52, Jeff Cody wrote:
> >Use the block layer to create, and write to, the image file in the
> >VDI .bdrv_create() operation.
> >
> >This has a couple of benefits: Images can now be created over protocols,
> >and hacks such as NOCOW are not needed in the image format driver, and
> >the underlying file protocol appropriate for the host OS can be relied
> 
> This sounds a bit strange to me, but I don't know if it's wrong.
>

You find the wording strange, or the logic itself?  If the latter, the
use of the posix calls (open(), write()) means that we cannot create
images over protocols such as gluster - so using the qemu block layer
operations instead means protocols are now supported.  And NOCOW is
not needed in the image format driver now, since raw-posix does the
same thing (if the bs->file protocol driver is a host file on a posix
system).

> >upon.
> >
> >Also some minor cleanup for error handling.
> >
> >Signed-off-by: Jeff Cody <jcody@redhat.com>
> >---
> >  block/vdi.c | 68 ++++++++++++++++++++++++++-----------------------------------
> >  1 file changed, 29 insertions(+), 39 deletions(-)
> >
> >diff --git a/block/vdi.c b/block/vdi.c
> >index 197bd77..5fd9d5f 100644
> >--- a/block/vdi.c
> >+++ b/block/vdi.c
> >@@ -681,7 +681,6 @@ static int vdi_co_write(BlockDriverState *bs,
> 
> Anyway:
> 
> Reviewed-by: Max Reitz <mreitz@redhat.com>

  reply	other threads:[~2014-07-22 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 19:52 [Qemu-devel] [PATCH v2 0/5] Allow VPC and VDI to be created over protocols Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 1/5] block: allow bdrv_unref() to be passed NULL pointers Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 2/5] block: vdi - use block layer ops in vdi_create, instead of posix calls Jeff Cody
2014-07-22 20:14   ` Max Reitz
2014-07-22 20:19     ` Jeff Cody [this message]
2014-07-22 20:20       ` Max Reitz
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 3/5] block: use the standard 'ret' instead of 'result' Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 4/5] block: vpc - use block layer ops in vpc_create, instead of posix calls Jeff Cody
2014-07-21 19:52 ` [Qemu-devel] [PATCH v2 5/5] block: iotest - update 084 to test static VDI image creation Jeff Cody
2014-07-22 20:21   ` Max Reitz
2014-07-22 20:24     ` Jeff Cody

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=20140722201924.GA31882@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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).