From: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>
To: Akihiko Odaki <akihiko.odaki@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v2 0/2] Create menus in iothread
Date: Sun, 20 Mar 2022 22:46:56 +0100 [thread overview]
Message-ID: <316ad12b-1cd6-b4d0-ad69-fd4759ea67d8@gmail.com> (raw)
In-Reply-To: <20220307134946.61407-1-akihiko.odaki@gmail.com>
On 7/3/22 14:49, Akihiko Odaki wrote:
> ui/cocoa: Create menus in iothread
>
> Commit 0439c5a4623d674efa0c72abd62ca6e98bb7cf87 introduced an
> assertion that blk_all_next is called in the main thread. The function
> is called in the following chain:
> - blk_all_next
> - qmp_query_block
> - addRemovableDevicesMenuItems
> - main
>
> This change moves the menu creation to the iothread. This also changes
> the menu creation procedure to construct the entire menu tree before
> setting to NSApp, which is necessary because a menu set once cannot be
> modified if NSApp is already running.
>
> v2: Separate a change moving create_initial_menus (Peter Maydell)
>
> Akihiko Odaki (2):
> ui/cocoa: Move create_initial_menus
> ui/cocoa: Create menus in iothread
Patch #2 doesn't apply anymore, can you respin?
prev parent reply other threads:[~2022-03-20 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 13:49 [PATCH v2 0/2] Create menus in iothread Akihiko Odaki
2022-03-07 13:49 ` [PATCH v2 1/2] ui/cocoa: Move create_initial_menus Akihiko Odaki
2022-03-07 13:49 ` [PATCH v2 2/2] ui/cocoa: Create menus in iothread Akihiko Odaki
2022-03-07 15:32 ` [PATCH v2 0/2] " Paolo Bonzini
2022-03-07 15:59 ` Akihiko Odaki
2022-03-20 21:46 ` 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=316ad12b-1cd6-b4d0-ad69-fd4759ea67d8@gmail.com \
--to=philippe.mathieu.daude@gmail.com \
--cc=akihiko.odaki@gmail.com \
--cc=kraxel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).