From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Barcelo <abarcelo@ac.upc.edu>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Coroutines and ucontext
Date: Tue, 07 Feb 2012 17:23:01 +0100 [thread overview]
Message-ID: <4F314FE5.1040400@redhat.com> (raw)
In-Reply-To: <CAFKAgTcHkMoAvy3ccjx_=n+TU2he0m=i4eve-A2DG6QVYTk80w@mail.gmail.com>
On 02/07/2012 05:06 PM, Alex Barcelo wrote:
> Yes, I agree. But makecontext and swapcontext are not OK for my
> project (mainly because makecontext and swapcontext are not supported
> by qemu under PPC) so I was looking for alternatives. My best shot at
> the moment is using sigaltstack, if it works I will post a patch for
> coroutines using sigaltstack, which is also quite portable (GNU
> Portable Thread can use both, so I was trying to copy its
> functionality).
If you get stuck you can use the coroutine-fix branch at
git://github.com/bonzini/qemu.git
Paolo
prev parent reply other threads:[~2012-02-07 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 12:39 [Qemu-devel] Coroutines and ucontext Alex Barcelo
2012-01-27 14:39 ` Paolo Bonzini
2012-01-27 14:48 ` Daniel P. Berrange
2012-01-28 9:31 ` Alex Barcelo
2012-02-07 11:18 ` Stefan Hajnoczi
2012-02-07 16:06 ` Alex Barcelo
2012-02-07 16:23 ` Paolo Bonzini [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=4F314FE5.1040400@redhat.com \
--to=pbonzini@redhat.com \
--cc=abarcelo@ac.upc.edu \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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 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.