From: Nolan <nolan@sigbus.net>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] add bdrv->create function for host_device
Date: Thu, 26 Mar 2009 17:03:36 -0700 [thread overview]
Message-ID: <1238112216.15350.235.camel@voxel> (raw)
In-Reply-To: 49CB7EED.7070706@us.ibm.com
Anthony Liguori writes:
> I'm not quite sure how, but I think you need to have BDRV_O_FILE as a
> special case. I think probably the easiest thing to do is to bail
> out if BDRV_O_FILE is set since a physical device cannot be growable.
If I understand you correctly, my original patch already does that:
if (flags || backing_file)
return -ENOTSUP;
Though I can't say that I'm entirely sure I understand what it means to
pass BDRV_O_FILE to bdrv_create().
The consensus of other block_*.c implementations is to ignore flags
completely or bail if flags != 0, unless they have their own bdrv
specific flags (eg BLOCK_FLAG_COMPAT6 for vmdk, and BLOCK_FLAG_ENCRYPT
for qcow/qcow2) which they specifically honor and ignore any other
flags.
next reply other threads:[~2009-03-27 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 0:03 Nolan [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-17 2:57 [Qemu-devel] [PATCH] add bdrv->create function for host_device Nolan
2009-03-26 13:11 ` Anthony Liguori
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=1238112216.15350.235.camel@voxel \
--to=nolan@sigbus.net \
--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).