qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: libvir-list@redhat.com, aliguori@us.ibm.com,
	Eric Blake <eblake@redhat.com>,
	stefanha@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 1/4] qemu-options: Add -filefd command line option
Date: Tue, 22 May 2012 15:38:18 +0200	[thread overview]
Message-ID: <4FBB96CA.3010500@redhat.com> (raw)
In-Reply-To: <4FBB93BC.9080901@linux.vnet.ibm.com>

Am 22.05.2012 15:25, schrieb Corey Bryant:
> 
> 
> On 05/21/2012 05:40 PM, Eric Blake wrote:
>> On 05/21/2012 02:19 PM, Corey Bryant wrote:
>>> This patch provides support for the -filefd command line option.
>>> This option will allow passing of a filename and its corresponding
>>> file descriptor to QEMU at exec time.
>>>
>>> Signed-off-by: Corey Bryant<coreyb@linux.vnet.ibm.com>
>>
>>> +DEF("filefd", HAS_ARG, QEMU_OPTION_filefd,
>>> +    "-filefd file=<filename>,fd=<fd>\n"
>>
>> I take it that if filename contains ',', then we have to escape it on
>> the command line?  Is it worth passing fd first and file second by
>> default, as a possible way to avoid the need for escaping, or does the
>> option parser not care about ordering?
>>
> 
> That's a good question.  The options can be ordered either way so I 
> don't think we'll force fd to be specified first.  I imagine this should 
> behave no differently than "-drive file=xyz,if=none,...".  I ran a quick 
> test using -drive with a filename that had a comma, and (escaped or not) 
> it failed on the option parsing.  So it looks like if you have a path 
> with a comma you're not going to have any luck.

I think you can escape it, you'd have to use a double comma. But I'd
rather not introduce more of this. It's another good reason for using
/dev/fd/... instead of a translation table.

Kevin

  reply	other threads:[~2012-05-22 13:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 20:19 [Qemu-devel] [RFC PATCH 0/4] block: file descriptor passing using -filefd and getfd_file Corey Bryant
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 1/4] qemu-options: Add -filefd command line option Corey Bryant
2012-05-21 21:40   ` Eric Blake
2012-05-22 13:25     ` Corey Bryant
2012-05-22 13:38       ` Kevin Wolf [this message]
2012-05-22 14:26         ` Stefan Hajnoczi
2012-05-22 14:39           ` Kevin Wolf
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 2/4] qmp/hmp: Add getfd_file monitor command Corey Bryant
2012-05-21 21:48   ` Eric Blake
2012-05-22 13:37     ` Corey Bryant
2012-05-22  9:18   ` Stefan Hajnoczi
2012-05-22 14:13     ` Corey Bryant
2012-05-22 19:06     ` Luiz Capitulino
2012-05-22 20:02       ` Corey Bryant
2012-05-22 20:26         ` Luiz Capitulino
2012-05-22 22:34           ` Corey Bryant
2012-05-23 13:33             ` Luiz Capitulino
2012-05-23 13:45               ` Corey Bryant
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 3/4] block: Enable QEMU to retrieve passed fd before attempting open Corey Bryant
2012-05-21 21:50   ` Eric Blake
2012-05-22 14:06     ` Corey Bryant
2012-05-21 20:19 ` [Qemu-devel] [RFC PATCH 4/4] Example -filefd and getfd_file server Corey Bryant
2012-05-22  8:18 ` [Qemu-devel] [RFC PATCH 0/4] block: file descriptor passing using -filefd and getfd_file Kevin Wolf
2012-05-22 12:02   ` Eric Blake
2012-05-22 12:08     ` Kevin Wolf
2012-05-22 14:30   ` Corey Bryant
2012-05-22 14:45     ` Kevin Wolf
2012-05-22 15:01       ` Eric Blake
2012-05-22 15:24         ` Kevin Wolf
2012-05-22 15:29       ` Corey Bryant
2012-05-22 15:39         ` Kevin Wolf
2012-05-22 16:02           ` Corey Bryant
2012-05-22 16:15         ` Eric Blake
2012-05-22 17:17           ` Corey Bryant

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=4FBB96CA.3010500@redhat.com \
    --to=kwolf@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=eblake@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.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 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).