From: Alexander Graf <agraf@suse.de>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: Add binfmt wrapper
Date: Mon, 14 Jul 2014 18:54:27 +0200 [thread overview]
Message-ID: <53C40B43.402@suse.de> (raw)
In-Reply-To: <OF6AE6F6BB.DF0A0B7B-ONC1257D15.005C5C3E-C1257D15.005C9B9D@transmode.se>
On 14.07.14 18:51, Joakim Tjernlund wrote:
> Alexander Graf <agraf@suse.de> wrote on 2014/07/14 18:34:34:
>>
>> On 14.07.14 18:32, Joakim Tjernlund wrote:
>>> Alexander Graf <agraf@suse.de> wrote on 2014/07/14 18:00:35:
>>> You think everyone feel OK with new defaults like OP ?
>>>> Yes.
>>> hmm, with current qemu it works to boot a LXC with just O flag.
>>> Why would we then want to complicate things by adding OP which
>>> then requires some version of my patch?
>> How does current QEMU boot anything with the 0 flag? It doesn't know how
>> to handle it and will misinterpret the argument, no?
> Playing some, one could possibly do both:
>
> - if (i > 0 && strcmp(binfmt, "-binfmt-wrapper") == 0) {
> + execfd = qemu_getauxval(AT_EXECFD);
> + if (execfd > 0 || i > 0 && strcmp(binfmt, "-binfmt-wrapper") == 0) {
0 is a valid fd :). And yes, this would work, but I don't see why we
should introduce the -binfmt-wrapper logic to upstream QEMU. It's never
been there. And the AT_EXECFD evaluation is a lot cleaner.
While we're at it - should we also pass the C flag to binfmt_misc?
Alex
next prev parent reply other threads:[~2014-07-14 16:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 14:38 [Qemu-devel] [PATCH] linux-user: Add binfmt wrapper Joakim Tjernlund
2014-07-14 15:21 ` Alexander Graf
2014-07-14 15:38 ` Joakim Tjernlund
2014-07-14 15:46 ` Alexander Graf
2014-07-14 15:59 ` Joakim Tjernlund
2014-07-14 16:00 ` Alexander Graf
2014-07-14 16:32 ` Joakim Tjernlund
2014-07-14 16:34 ` Alexander Graf
2014-07-14 16:45 ` Joakim Tjernlund
2014-07-14 16:51 ` Joakim Tjernlund
2014-07-14 16:54 ` Alexander Graf [this message]
2014-07-14 17:01 ` Joakim Tjernlund
2014-07-14 17:08 ` Joakim Tjernlund
2014-07-14 17:14 ` Alexander Graf
2014-07-14 16:00 ` Peter Maydell
2014-07-14 16:08 ` Joakim Tjernlund
2014-07-15 14:12 ` Riku Voipio
2014-07-15 14:39 ` Joakim Tjernlund
2014-07-15 15:11 ` Joakim Tjernlund
2014-07-16 6:54 ` Riku Voipio
2014-07-16 7:22 ` Joakim Tjernlund
2014-07-16 11:38 ` Joakim Tjernlund
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=53C40B43.402@suse.de \
--to=agraf@suse.de \
--cc=joakim.tjernlund@transmode.se \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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.