All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	Peter Maydell <peter.maydell@linaro.org>,
	Elisey Konstantinov <elisey.konstantinov@gmail.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
	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 19:28:38 -0300	[thread overview]
Message-ID: <87a4usdmcp.fsf@suse.de> (raw)
In-Reply-To: <a4fd79f8-43fa-4894-80d3-ed31ffec1ff6@ilande.co.uk>

Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> writes:

> On 24/04/2026 12:51, Peter Maydell wrote:
>
>> The "New World" and "Old World" machines are listed in our
>> MAINTAINERS file as "Odd Fixes", which means:
>> 
>> "It has a maintainer but they don't have time to do
>>   much other than throw the odd patch in."
>> 
>> In other words, there is no active development work ongoing,
>> and nobody with time and interest to investigate complex bugs.
>> If it happens to work for people, that's great. If it doesn't
>> work and somebody proposes a patch then we can review the patch
>> (as we have done for this one). If it doesn't work and nobody
>> proposes a satisfactory patch then it will likely remain broken.
>
> I'm around to do various small bits and pieces, but at least for the short term it's 
> fairly hard to find the extended time that bugs like these require.
>
> Note that MacOS X before 10.2 (including MacOS 9) appear to be timing sensitive to 
> the CUDA interrupts, so that might be another explanation. You could try 
> experimenting with increasing the delay at 
> https://gitlab.com/qemu-project/qemu/-/blob/master/hw/misc/macio/cuda.c?ref_type=heads#L537 
> to see if that helps?
>

Hi, just to let you all know I cannot reproduce this.

MacOS X boots past the initial screen, the installer comes up and
clicking around works fine. With both QEMU 10.0.0 and current master.


  reply	other threads:[~2026-04-24 22:29 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é
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 [this message]
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=87a4usdmcp.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=berrange@redhat.com \
    --cc=elisey.konstantinov@gmail.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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.