From: Paolo Bonzini <pbonzini@redhat.com>
To: "Joelle van Dyne" <j@getutm.app>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] coroutine: add libucontext as external library
Date: Tue, 9 Mar 2021 11:24:08 +0100 [thread overview]
Message-ID: <537a6a0e-431b-3920-c8dc-290e4e3d8895@redhat.com> (raw)
In-Reply-To: <CA+E+eSBt5sq08zfxLOZKNQd=A3q=9YLEt0moipTb7j+OGWyuRg@mail.gmail.com>
On 09/03/21 10:59, Joelle van Dyne wrote:
> Does it make a difference if this is provided as an option and not as
> a replacement? Would it make sense to add some warning at configure
> time? Right now none of the concurrency backends are supported on iOS
> and it's possible support will go away on macOS as well in the future.
> QEMU would not be able to run at all.
The alternative is to use a handwritten backend, it would be necessary
anyway for CET support.
You can find the patches at
https://patchew.org/QEMU/20190504120528.6389-1-pbonzini@redhat.com/
Paolo
next prev parent reply other threads:[~2021-03-09 10:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 3:26 [PATCH] coroutine: add libucontext as external library Joelle van Dyne
2021-03-09 9:35 ` Daniel P. Berrangé
2021-03-09 9:59 ` Joelle van Dyne
2021-03-09 10:20 ` Peter Maydell
2021-03-09 10:32 ` Daniel P. Berrangé
2021-03-09 10:24 ` Paolo Bonzini [this message]
2021-03-09 10:29 ` Daniel P. Berrangé
2021-03-09 10:42 ` Marc-André Lureau
2021-03-09 10:48 ` Paolo Bonzini
2021-03-09 15:38 ` Stefan Hajnoczi
2021-03-09 18:24 ` Joelle van Dyne
2021-03-09 21:21 ` Joelle van Dyne
2021-03-10 9:29 ` Daniel P. Berrangé
2021-03-10 16:32 ` Joelle van Dyne
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=537a6a0e-431b-3920-c8dc-290e4e3d8895@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=j@getutm.app \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).