From: Eric Blake <eblake@redhat.com>
To: "Benoît Canet" <benoit@irqsave.net>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2] block: introduce BlockDriver.bdrv_needs_filename to enable some drivers.
Date: Mon, 23 Sep 2013 09:59:27 -0600 [thread overview]
Message-ID: <5240655F.6080301@redhat.com> (raw)
In-Reply-To: <1379937171-32128-2-git-send-email-benoit@irqsave.net>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On 09/23/2013 05:52 AM, Benoît Canet wrote:
> Some drivers will have driver specifics options but no filename.
> This new bool allow the block layer to treat them correctly.
>
> The .bdrv_needs_filename is set in drivers not having .bdrv_parse_filename and
> not having .bdrv_open.
>
> The first exception to this rule will be the quorum driver.
>
> Signed-off-by: Benoit Canet <benoit@irqsave.net>
> ---
> +++ b/include/block/block_int.h
> @@ -73,6 +73,7 @@ struct BlockDriver {
> /* Any driver implementing this callback is expected to be able to handle
> * NULL file names in its .bdrv_open() implementation */
> void (*bdrv_parse_filename)(const char *filename, QDict *options, Error **errp);
> + bool bdrv_needs_filename;
Please use inline comments documenting this field's use.
>
> /* For handling image reopen for split or non-split files */
> int (*bdrv_reopen_prepare)(BDRVReopenState *reopen_state,
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
prev parent reply other threads:[~2013-09-23 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 11:52 [Qemu-devel] [PATCH V2] introduce .bdrv_needs_filename Benoît Canet
2013-09-23 11:52 ` [Qemu-devel] [PATCH V2] block: introduce BlockDriver.bdrv_needs_filename to enable some drivers Benoît Canet
2013-09-23 15:59 ` Eric Blake [this message]
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=5240655F.6080301@redhat.com \
--to=eblake@redhat.com \
--cc=benoit@irqsave.net \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.