All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: libvir-list@redhat.com, kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] command line fd passing using fd sets
Date: Fri, 05 Oct 2012 14:37:53 -0400	[thread overview]
Message-ID: <506F2901.7030901@linux.vnet.ibm.com> (raw)
In-Reply-To: <506F2648.2020605@redhat.com>



On 10/05/2012 02:26 PM, Eric Blake wrote:
> On 10/05/2012 12:07 PM, Corey Bryant wrote:
>> This series adds command line file descriptor passing support
>> to the -drive option.  This is a follow-on to the existing
>> QMP fd passing support provided in the following patch series:
>> comments.gmane.org/gmane.comp.emulators.qemu/165463
>>
>> An example of using the new -drive fd and opaque options:
>> qemu-kvm -drive fd=24,opaque="rdwr:/path/file",index=0,media=disk
>
> This feels wrong.  Now you have to special-case encode the
> fd=nn,opaque=xyz handling to EVERY command line argument that takes a
> file name, not just -drive.
>
> I'd much rather see:
>
> qemu-kvm -fdset set=1,fds=24,25 \
>    -drive file=/def/fdset/1,index=0,media=disk
>
> Where the creation of fdsets happens independently from use of those
> sets, and therefore all other arguments that take file names can just
> magically take the /dev/fdset/nnn notation that we already support from
> the monitor.
>
> Besides, my approach will let me pass in an O_RDONLY fd on 24 and O_RDWR
> on 25 into the same set, whereas your approach creates a new set per fd,
> so I can't add new fds to the set until the monitor is up and running.
>

Thanks for the quick feedback.  I like your idea here.  Much more flexible.

-- 
Regards,
Corey Bryant

      reply	other threads:[~2012-10-05 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 18:07 [Qemu-devel] [PATCH 0/4] command line fd passing using fd sets Corey Bryant
2012-10-05 18:07 ` [Qemu-devel] [PATCH 1/4] monitor: Less restrictive fd matching for " Corey Bryant
2012-10-05 18:35   ` Eric Blake
2012-10-05 18:50     ` Corey Bryant
2012-10-05 18:07 ` [Qemu-devel] [PATCH 2/4] monitor: Enable adding an inherited fd to an fd set Corey Bryant
2012-10-05 18:07 ` [Qemu-devel] [PATCH 3/4] qemu-config: Add -drive fd and opaque options Corey Bryant
2012-10-05 18:25   ` Blue Swirl
2012-10-05 18:30     ` Eric Blake
2012-10-05 18:44       ` Corey Bryant
2012-10-05 18:51         ` Eric Blake
2012-10-05 18:57           ` Corey Bryant
2012-10-05 18:48     ` Corey Bryant
2012-10-05 18:07 ` [Qemu-devel] [PATCH 4/4] blockdev: Process " Corey Bryant
2012-10-05 18:26 ` [Qemu-devel] [PATCH 0/4] command line fd passing using fd sets Eric Blake
2012-10-05 18:37   ` Corey Bryant [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=506F2901.7030901@linux.vnet.ibm.com \
    --to=coreyb@linux.vnet.ibm.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=libvir-list@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 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.