qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-io: add flag to mark files growable
Date: Mon, 6 Jul 2009 12:20:24 +0200	[thread overview]
Message-ID: <20090706102023.GA7835@lst.de> (raw)
In-Reply-To: <4A51BBA1.4090307@redhat.com>

On Mon, Jul 06, 2009 at 10:53:53AM +0200, Kevin Wolf wrote:
> Christoph Hellwig schrieb:
> > Add a -g flag to the open command and the main qemu-io command line to
> > allow opening a file growable.  This is only allowed for protocols,
> > mirroring the limitation exposed through bdrv_file_open.
> 
> This limitation doesn't look quite right. I'm not sure if growable
> images are used anywhere else, too, but their main usage is for the
> image file access in formats like qcow - that is, growable images are
> usually raw. And raw didn't have a protocol name until recently.

It does have a protocol now, and the way current qemu is implemented
growable is only set from bdrv_file_open, which implies the BDRV_O_FILE
argument to bdrv_open2, which means we use find_protocol to find the
BlockDriver and find_protocol needs protocol_name set.

If you want to backport this patch to a qemu version that doesn't
have a protocol_name for raw you'll have to adjust it to whatever check
is correct in that version.

  reply	other threads:[~2009-07-06 10:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-04 15:53 [Qemu-devel] [PATCH] qemu-io: add flag to mark files growable Christoph Hellwig
2009-07-06  8:53 ` Kevin Wolf
2009-07-06 10:20   ` Christoph Hellwig [this message]
2009-07-06 10:40     ` Kevin Wolf
2009-07-06 10:51       ` Christoph Hellwig
2009-07-06 11:04         ` Kevin Wolf
2009-07-06 11:14           ` Christoph Hellwig

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=20090706102023.GA7835@lst.de \
    --to=hch@lst.de \
    --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).