From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-io: add flag to mark files growable
Date: Mon, 06 Jul 2009 13:04:55 +0200 [thread overview]
Message-ID: <4A51DA57.3010600@redhat.com> (raw)
In-Reply-To: <20090706105111.GA9469@lst.de>
Christoph Hellwig schrieb:
> On Mon, Jul 06, 2009 at 12:40:06PM +0200, Kevin Wolf wrote:
>> Ok, you are right. raw was the only exception because it could be used
>> as a protocol even though it didn't have a protocol name.
>>
>> Looks fine to me then if you enforce the limitation instead of only
>> printing an error message and opening the image anyway. Not printing the
>> error and opening the image would be fine either. I just don't like
>> error messages without errors.
>
> Well, the primary use of qemu-iotests is to try out the I/O patterns,
> and the -g option is to check out we do the correct thing for growable
> files, so I'd really prefer it to fail if we're not allow to actually
> make it growable.
Perfectly reasonable. But then make it really fail.
> Now one think I could do is to just add a growable flag to the
> BlockDriver to make it explicit. Currently only raw files (in the posix
> and win32 flavours) would set it.
Good point actually, your current logic is wrong: raw-win32 doesn't have
the file protocol. I'm not sure though if introducing a new flag just
for qemu-io is right. After all qemu-io should test what the drivers
provide to qemu and not extend them to work with qemu-io. Currently the
drivers don't have the concept of non-growable images.
> That would also fix the bug what we
> currenly allow to grow host devices even if we can't.
How that? The host device drivers don't have a protocol name, do they?
Kevin
next prev parent reply other threads:[~2009-07-06 11:06 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
2009-07-06 10:40 ` Kevin Wolf
2009-07-06 10:51 ` Christoph Hellwig
2009-07-06 11:04 ` Kevin Wolf [this message]
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=4A51DA57.3010600@redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.