From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Elisey Konstantinov <elisey.konstantinov@gmail.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
marcandre.lureau@redhat.com, philmd@linaro.org
Subject: Re: [PATCH] build: prefer sigaltstack over ucontext on Linux
Date: Fri, 24 Apr 2026 09:57:11 +0100 [thread overview]
Message-ID: <aeswZxFn0zMj-3jb@redhat.com> (raw)
In-Reply-To: <616E96C0-F0A5-4A9E-A63B-3BC1B5F18094@gmail.com>
On Fri, Apr 24, 2026 at 11:19:39AM +0300, Elisey Konstantinov wrote:
> From 517099e65de1e2ad3d0f33d3c4a7a71f8728279c Mon Sep 17 00:00:00 2001
> From: Elisey <elisey.konstantinov@gmail.com>
> Date: Mon, 23 Mar 2026 16:02:45 +0100
> Subject: [PATCH] build: prefer sigaltstack over ucontext on Linux
>
> sigaltstack coroutine backend is more stable on some Linux
> configurations, while ucontext causes boot failures for certain
> PPC Mac OS X guests (issue #3276).
> Select sigaltstack first when available, keeping ucontext as fallback
> until the underlying issue is resolved.
IMHO there needs to be a greater investigation in to why ucontext
would be demonstrating the failure. ucontext has been the default
on Linux for QEMU for decades without significant issues, so my
concern is that switching to sigaltstack is not fixing the root
cause of the bug you see, just masking it by luck.
The choice of coroutine backend can also be performance sensitive
and so changing it is something that would need to also bring
along performance benchmark data to illustrate the likely impact
of the change.
>
> Signed-off-by: Elisey Konstantinov <elisey.konstantinov@gmail.com>
> ---
> meson.build | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index ab3e97eb9f..742655e007 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -505,10 +505,12 @@ if host_os == 'windows'
> elif host_os == 'emscripten'
> supported_backends += ['wasm']
> else
> + # FIXME: This is a temporary workaround!
> + # SigAltStack is in higher priority to fix #3276
> + supported_backends += ['sigaltstack']
> if host_os != 'darwin' and cc.links(ucontext_probe)
> supported_backends += ['ucontext']
> endif
> - supported_backends += ['sigaltstack']
> endif
>
> if coroutine_backend == 'auto'
> --
> 2.50.1 (Apple Git-155)
>
next prev parent reply other threads:[~2026-04-24 8:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 8:19 [PATCH] build: prefer sigaltstack over ucontext on Linux Elisey Konstantinov
2026-04-24 8:57 ` Daniel P. Berrangé [this message]
2026-04-24 9:19 ` Elisey Konstantinov
2026-04-24 9:32 ` Daniel P. Berrangé
2026-04-24 11:31 ` Elisey Konstantinov
2026-04-24 11:51 ` Peter Maydell
2026-04-24 19:52 ` Mark Cave-Ayland
2026-04-24 22:28 ` Fabiano Rosas
2026-04-27 6:56 ` Elisey Konstantinov
2026-04-27 15:18 ` Fabiano Rosas
2026-04-29 13:36 ` Fabiano Rosas
2026-04-27 7:00 ` Elisey Konstantinov
2026-04-24 12:03 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2026-04-24 15:38 elisey.konstantinov
2026-04-24 16:22 elisey.konstantinov
2026-04-24 20:02 ` Paolo Bonzini
2026-04-27 8:12 Elisey Konstantinov
2026-04-27 8:18 ` Elisey Konstantinov
2026-04-27 8:30 ` Elisey Konstantinov
2026-04-27 15:30 elisey.konstantinov
2026-04-29 13:46 ` Daniel P. Berrangé
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=aeswZxFn0zMj-3jb@redhat.com \
--to=berrange@redhat.com \
--cc=elisey.konstantinov@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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.