From: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, akihiko.odaki@gmail.com
Subject: Re: [RFC uncompiled PATCH] cocoa: run qemu_init in the main thread
Date: Wed, 16 Mar 2022 17:02:32 +0100 [thread overview]
Message-ID: <dbecd60e-9c63-11b8-76fc-4ceda7efa3f4@gmail.com> (raw)
In-Reply-To: <20220307151004.578069-1-pbonzini@redhat.com>
On 7/3/22 16:10, Paolo Bonzini wrote:
> Simplify the initialization dance by running qemu_init() in the main
> thread before the Cocoa event loop starts. The cocoa_display_init()
> code that is post-applicationDidFinishLaunching: moves to the
> application delegate itself, and the secondary thread only runs
> the rest of qemu_main(), namely qemu_main_loop() and qemu_cleanup().
>
> This fixes a case where addRemovableDevicesMenuItems() calls
> qmp_query_block() while expecting the main thread to still hold
> the BQL. The newly-introduced assertions in the block layer
> complain about this.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> softmmu/main.c | 12 +++--
> ui/cocoa.m | 122 +++++++++++++++++++------------------------------
> 2 files changed, 53 insertions(+), 81 deletions(-)
I got this building and it indeed fixes the issue reported here:
https://lore.kernel.org/qemu-devel/cecef6bd-951a-aab6-e603-96e3551e3e9e@gmail.com/
I will post as v2 and let you iterate :)
prev parent reply other threads:[~2022-03-16 16:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 15:10 [RFC uncompiled PATCH] cocoa: run qemu_init in the main thread Paolo Bonzini
2022-03-07 15:34 ` Akihiko Odaki
2022-03-07 16:14 ` Peter Maydell
2022-03-07 16:27 ` Akihiko Odaki
2022-03-07 16:35 ` Peter Maydell
2022-03-07 16:41 ` Akihiko Odaki
2022-03-07 17:21 ` Paolo Bonzini
2022-03-07 19:25 ` Akihiko Odaki
2022-03-07 16:39 ` Paolo Bonzini
2022-03-07 17:03 ` Akihiko Odaki
2022-03-07 17:06 ` Paolo Bonzini
2022-03-16 16:02 ` Philippe Mathieu-Daudé [this message]
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=dbecd60e-9c63-11b8-76fc-4ceda7efa3f4@gmail.com \
--to=philippe.mathieu.daude@gmail.com \
--cc=akihiko.odaki@gmail.com \
--cc=pbonzini@redhat.com \
--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.