From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: libvir-list@redhat.com, Tyler C Hicks <tchicks@us.ibm.com>,
Corey C Bryant <bryntcor@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Add support for fd: protocol
Date: Tue, 21 Jun 2011 11:21:03 +0300 [thread overview]
Message-ID: <4E00546F.3000103@redhat.com> (raw)
In-Reply-To: <4DFF9B4C.1080804@us.ibm.com>
On 06/20/2011 10:11 PM, Anthony Liguori wrote:
>> It would need careful explanation in the management tool author's guide,
>> yes.
>>
>> The main advantage is generality. It doesn't assume that a file format
>> has just one backing file, and doesn't require new syntax wherever a
>> file is referred to indirectly.
>
>
> FWIW, with blockdev, we need options to control this all anyway. If
> you go back to my QCFG proposal, the parameters would actually be
> format specific, so if we had:
>
> -block
> file=fd:4,format=fancypantsformat,part0=hd0-back.part1,part1=hd0-back.part2...
Yeah. We either name the formal argument (your proposal) or the actual
argument (mine).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-06-21 8:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 13:31 [Qemu-devel] [PATCH v2] Add support for fd: protocol Corey Bryant
2011-06-14 16:13 ` [Qemu-devel] [libvirt] " Eric Blake
2011-06-14 19:55 ` Corey Bryant
2011-06-14 20:18 ` Eric Blake
2011-06-14 21:39 ` Corey Bryant
2011-06-14 21:52 ` Eric Blake
2011-06-15 19:12 ` [Qemu-devel] " Blue Swirl
2011-06-16 14:48 ` Corey Bryant
2011-06-18 20:50 ` Blue Swirl
2011-06-20 13:08 ` Corey Bryant
2011-06-20 13:40 ` Avi Kivity
2011-06-20 13:50 ` Anthony Liguori
2011-06-20 17:35 ` Avi Kivity
2011-06-20 19:11 ` Anthony Liguori
2011-06-21 8:21 ` Avi Kivity [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=4E00546F.3000103@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=bryntcor@us.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tchicks@us.ibm.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.