From: Anthony Liguori <anthony@codemonkey.ws>
To: Ronnie Sahlberg <ronniesahlberg@gmail.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] readconfig: add emulation of /dev/fd/ to platforms that that lacks this API
Date: Mon, 19 Mar 2012 11:43:43 -0500 [thread overview]
Message-ID: <4F67623F.2010304@codemonkey.ws> (raw)
In-Reply-To: <1330760957-17122-1-git-send-email-ronniesahlberg@gmail.com>
On 03/03/2012 01:49 AM, Ronnie Sahlberg wrote:
> Please find a patch to -readconfig.
>
> On many platforms -readconfig /dev/fd/<n> can be used to read from an already opened and inherited filedescriptor<n>.
>
> On platforms that do not natively provide /dev/fd/<n>
What platforms don't provide /dev/fd/<n> where fd passing makes sense?
Regards,
Anthony Liguori
> add emulation of this by checking if the ofiginal fopen(path) failed, then IF
> the path starts with /dev/fd/ then try to read the descriptorvalue and fdopen() it.
>
>
> It means that we can use -readconfig /dev/fd/<n> on all platforms. On those that provide a /dev/fd we just open that file. On those that do not we emulate it.
>
>
> regards
> ronnie sahlberg
>
>
next prev parent reply other threads:[~2012-03-19 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 7:49 [Qemu-devel] [PATCH] readconfig: add emulation of /dev/fd/ to platforms that that lacks this API Ronnie Sahlberg
2012-03-03 7:49 ` [Qemu-devel] [PATCH] READCONFIG: allow /dev/fd/ the file to use for --readconfig Ronnie Sahlberg
2012-03-19 16:43 ` Anthony Liguori [this message]
2012-03-20 8:02 ` [Qemu-devel] [PATCH] readconfig: add emulation of /dev/fd/ to platforms that that lacks this API ronnie sahlberg
-- strict thread matches above, loose matches on Subject: below --
2012-03-03 7:57 Ronnie Sahlberg
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=4F67623F.2010304@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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).