From: Andreas Schwab <schwab@suse.de>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Helge Deller <deller@gmx.de>,
qemu-devel@nongnu.org
Subject: Re: Generic way to detect qemu linux-user emulation
Date: Tue, 18 Mar 2025 15:17:33 +0100 [thread overview]
Message-ID: <mvmh63qh18i.fsf@suse.de> (raw)
In-Reply-To: <Z9l7J0oZ8GAEqaMP@redhat.com> ("Daniel P. Berrangé"'s message of "Tue, 18 Mar 2025 13:54:47 +0000")
On Mär 18 2025, Daniel P. Berrangé wrote:
> That would get the synchronization behaviour of Linux vfork,
> but I'm not sure it'd get the performance benefits (of avoiding
> page table copying) which is what Andreas mentioned as the
> desired thing ?
For an emulation performance isn't a thing, what we need is accuracy.
The current issue I have right now is that the MozillaFirefox package
fails to build because posix_spawn behaves unexpectedly.
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/MozillaFirefox/standard/riscv64
[ 666s] 4:55.15 Traceback (most recent call last):
[ 666s] 4:55.16 File "/home/abuild/rpmbuild/BUILD/MozillaFirefox-136.0.1-build/firefox-136.0.1/security/nss/./coreconf/werror.py", line 80, in <module>
[ 666s] 4:55.16 main()
[ 666s] 4:55.16 ~~~~^^
[ 666s] 4:55.16 File "/home/abuild/rpmbuild/BUILD/MozillaFirefox-136.0.1-build/firefox-136.0.1/security/nss/./coreconf/werror.py", line 10, in main
[ 666s] 4:55.16 cc_is_clang = 'clang' in subprocess.check_output(
[ 666s] 4:55.16 ~~~~~~~~~~~~~~~~~~~~~~~^
[ 666s] 4:55.16 [cc, '--version'], universal_newlines=True, stderr=sink)
[ 666s] 4:55.16 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 666s] 4:55.16 File "/usr/lib64/python3.13/subprocess.py", line 474, in check_output
[ 666s] 4:55.16 return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
[ 666s] 4:55.16 ~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ 666s] 4:55.17 **kwargs).stdout
[ 666s] 4:55.17 ^^^^^^^^^
[ 666s] 4:55.17 File "/usr/lib64/python3.13/subprocess.py", line 579, in run
[ 666s] 4:55.17 raise CalledProcessError(retcode, process.args,
[ 666s] 4:55.17 output=stdout, stderr=stderr)
[ 666s] 4:55.17 subprocess.CalledProcessError: Command '['/usr/bin/ccache /usr/bin/gcc', '--version']' returned non-zero exit status 127.
A real posix_spawn would have set errno to ENOENT.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2025-03-18 14:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:18 Generic way to detect qemu linux-user emulation Andreas Schwab
2025-03-18 10:36 ` Helge Deller
2025-03-18 10:45 ` Helge Deller
2025-03-18 10:53 ` Peter Maydell
2025-03-18 11:58 ` Daniel P. Berrangé
2025-03-18 12:34 ` Andreas Schwab
2025-03-18 12:43 ` Daniel P. Berrangé
2025-03-18 13:06 ` Peter Maydell
2025-03-18 13:54 ` Daniel P. Berrangé
2025-03-18 14:17 ` Andreas Schwab [this message]
2025-03-18 17:32 ` Daniel P. Berrangé
2025-03-18 15:04 ` Peter Maydell
2025-03-18 17:08 ` Peter Maydell
2025-03-18 17:18 ` Daniel P. Berrangé
2025-03-18 17:48 ` Peter Maydell
2026-03-25 17:08 ` Florian Weimer
2025-03-18 11:10 ` Andreas Schwab
2026-03-25 14:51 ` Lawrence Hunter
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=mvmh63qh18i.fsf@suse.de \
--to=schwab@suse.de \
--cc=berrange@redhat.com \
--cc=deller@gmx.de \
--cc=peter.maydell@linaro.org \
--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.