qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Chunyan Liu <cyliu@suse.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img create: add -o nocow option
Date: Thu, 21 Nov 2013 09:51:39 +0100	[thread overview]
Message-ID: <20131121085139.GG27039@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAERYnoYhDCzV-j9km8UCAT=-+m0ib_dyd0H70JG6qWgqPO7eaA@mail.gmail.com>

On Thu, Nov 21, 2013 at 11:33:56AM +0800, Chunyan Liu wrote:
> 2013/11/20 Stefan Hajnoczi <stefanha@gmail.com>
> 
> > On Wed, Nov 20, 2013 at 04:50:29PM +0800, Chunyan Liu wrote:
> > >  block/cow.c               |   22 ++++++++++++++++++++++
> > >  block/qcow.c              |   22 ++++++++++++++++++++++
> > >  block/qcow2.c             |   22 ++++++++++++++++++++++
> >
> > I think you can avoid modifying all the image formats:
> >
> > .bdrv_create() functions pass options to bdrv_create_file().  Therefore
> > an image format like qcow2 does not need to parse the nocow option
> > itself.  Only raw-posix.c:.bdrv_create() needs to know about the nocow
> > option.
> >
> >
> In existing code, options passed to bdrv_create_file contains no option in
> fact.
> 
> And if we pass all options to bdrv_create_file directly, raw-posix.c:
> .bdrv_create() will get NOCOW option but at the same time get SIZE option,
> it
> will create a file with total size. For cow/qcow/qcow2, I suppose it's not
> expected? In current code, bdrv_create_file will create a zero-sized image
> for
> cow/qcow/qcow2.

I see what the problem is: the loop that parses options does options++.
So by the time it has processed them the options pointer will be NULL or
point to a terminator option (option->name == NULL).

I was confused because there has been a patch series which changes
.bdrv_create() option parsing.  But I forgot it hasn't been merged.
https://lists.gnu.org/archive/html/qemu-devel/2013-08/msg01695.html

Kevin: Have you looked at .bdrv_create() QEMUOptionParameter removal
recently?  Otherwise I'm inclined to merge Chunyan's patch - we can
always refactor the code later when QEMUOptionParameter is removed.

Stefan

  reply	other threads:[~2013-11-21  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20  8:50 [Qemu-devel] [PATCH] qemu-img create: add -o nocow option Chunyan Liu
2013-11-20 15:15 ` Stefan Hajnoczi
2013-11-21  3:33   ` Chunyan Liu
2013-11-21  8:51     ` Stefan Hajnoczi [this message]
2013-11-25  8:09       ` Chunyan Liu
2013-11-25  9:21       ` Kevin Wolf
2013-12-02  3:54         ` Chunyan Liu
2013-12-04  9:20           ` Stefan Hajnoczi

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=20131121085139.GG27039@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=cyliu@suse.com \
    --cc=kwolf@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).