From: Kyle Evans <kevans@freebsd.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>,
ncopa@alpinelinux.org, "Warner Losh" <imp@bsdimp.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH] linux-user,bsd-user: re-exec with G_SLICE=always-malloc
Date: Thu, 6 Oct 2022 11:49:47 -0700 [thread overview]
Message-ID: <CACNAnaHN=xv14PycQ3_nvu60AkSyFc=mAXeh_EVcats8UnrbrA@mail.gmail.com> (raw)
In-Reply-To: <0d3f27ab-de02-c5b5-488f-08fb7e329bd8@linaro.org>
On Thu, Oct 6, 2022 at 11:29 AM Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> On 10/6/22 11:12, Daniel P. Berrangé wrote:
> > The only possible silver linining is that in static linked builds,
> > it appears that a QEMU constructor with priority 101, will pre-empt
> > the constructor from any library. This is kind of crazy, as it means
> > if any library or app code uses priorities, it'll get totally different
> > execution ordering depending on whether it is dynamic or statically
> > built.
>
> Plausible...
>
> > I guess we could rely on this hack if we declare that everyone using
> > binfmt is probably relying on static linked QEMU, and in non-binfmt
> > cases people can set the env var themselves. It still feels pretty
> > dirty.
>
> ... but as you say, dirty.
FWIW, on FreeBSD at least, we don't support dynamically linked
bsd-user and I'd go as far as to say that we have no desire to change
that in the future, either -- the benefits are simply not there to
outweigh the pain for our use-cases.
Thanks,
Kyle Evans
next prev parent reply other threads:[~2022-10-06 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 12:00 [PATCH] linux-user,bsd-user: re-exec with G_SLICE=always-malloc Daniel P. Berrangé
2022-10-04 12:05 ` Peter Maydell
2022-10-04 14:59 ` Richard Henderson
2022-10-06 18:12 ` Daniel P. Berrangé
2022-10-06 18:29 ` Richard Henderson
2022-10-06 18:49 ` Kyle Evans [this message]
2022-12-01 6:55 ` Emilio Cota
2022-12-01 10:49 ` Alex Bennée
2023-01-11 4:01 ` Emilio Cota
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='CACNAnaHN=xv14PycQ3_nvu60AkSyFc=mAXeh_EVcats8UnrbrA@mail.gmail.com' \
--to=kevans@freebsd.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=imp@bsdimp.com \
--cc=laurent@vivier.eu \
--cc=ncopa@alpinelinux.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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).