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 10:32:00 +0100 [thread overview]
Message-ID: <aes4kEdQ_x8eI-m6@redhat.com> (raw)
In-Reply-To: <06C2CFB8-BA33-46D6-9F84-B1F81A2A319E@gmail.com>
On Fri, Apr 24, 2026 at 12:19:19PM +0300, Elisey Konstantinov wrote:
> I completely agree, but in my opinion, investigating UContext will take a considerable amount of time, which is why I took the liberty of proposing this patch; in the commit message, I actually mention that this is merely a “temporary workaround”
>
> So, I suggest:
> - Merging the patch into the mainstream for the convenience of users (as, from what I’ve observed, SigAltStack is coping quite well with the task, at least for now...)
> - Whilst leaving #3276 open for the time being and continuing the UContext diagnostics there
> - And accordingly, as soon as UContext is fully functional, we can switch QEMU back from SigAltStack
>
> Also the another arrangement is to use UContext ONLY if PPC is in the build targets, but I am unable to do this, as my knowledge of Meson is insufficient for such a task; nevertheless, I would be grateful for any assistance :)
>
> P. S. Anticipating such a reaction, I DELIBERATELY did not include “Resolves” in the patch notes, so I am fully aware of all the proposed precautions
PPC MacOS guest is such a niche use case, that I don't see a compelling
reason to make such a change in git until the ticket has been fully
investigated and the problem root caused.
next prev parent reply other threads:[~2026-04-24 9:32 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é
2026-04-24 9:19 ` Elisey Konstantinov
2026-04-24 9:32 ` Daniel P. Berrangé [this message]
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=aes4kEdQ_x8eI-m6@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.