qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] coroutine: introduce coroutines
Date: Wed, 25 May 2011 11:54:43 -0700	[thread overview]
Message-ID: <4DDD5073.80601@twiddle.net> (raw)
In-Reply-To: <BANLkTikqsT2HK6cQTuY+i5cCOUYmFW+MSA@mail.gmail.com>

On 05/25/2011 12:09 AM, Stefan Hajnoczi wrote:
> On Tue, May 24, 2011 at 9:51 PM, Jamie Lokier <jamie@shareable.org> wrote:
>> Stefan Hajnoczi wrote:
>>> My current plan is to try using sigaltstack(2) instead of
>>> makecontext()/swapcontext() as a hack since OpenBSD doesn't have
>>> makecontext()/swapcontext().
>>
>> sigaltstack() is just a system call to tell the system about an
>> alternative signal stack - that you have allocated yourself using
>> malloc().  According to 'info libc "Signal Stack"'.  It won't help you
>> get a new stack by itself.
> 
> Issue sigaltstack() with the malloced new stack.  Send yourself a
> signal and in a custom signal handler setjmp() to stash away the state
> (you're now on the new stack).

Is any of this really easier than simply writing 20-30 lines of
assembly to do what you Really Want And Nothing Else?

Honestly, this is qemu we're talking about, and we assume you've
already ported TCG to the host cpu plus abi.  How hard is it to
just DTRT with a qemu-specific routine, anyway?


r~

  reply	other threads:[~2011-05-25 18:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 10:15 [Qemu-devel] [PATCH 0/2] Coroutines for better asynchronous programming Stefan Hajnoczi
2011-05-11 10:15 ` [Qemu-devel] [PATCH 1/2] coroutine: introduce coroutines Stefan Hajnoczi
2011-05-11 11:20   ` Kevin Wolf
2011-05-11 12:04   ` Paolo Bonzini
2011-05-11 12:15     ` Kevin Wolf
2011-05-11 12:51     ` Anthony Liguori
2011-05-11 12:52       ` Paolo Bonzini
2011-05-11 13:05         ` Anthony Liguori
2011-05-11 13:45           ` Paolo Bonzini
2011-05-11 13:51             ` Daniel P. Berrange
2011-05-24 19:37               ` Jamie Lokier
2011-05-24 19:58                 ` Stefan Hajnoczi
2011-05-24 20:51                   ` Jamie Lokier
2011-05-25  7:09                     ` Stefan Hajnoczi
2011-05-25 18:54                       ` Richard Henderson [this message]
2011-05-24 21:21                   ` Anthony Liguori
2011-05-25  7:32                     ` Paolo Bonzini
2011-05-24 21:22                   ` Anthony Liguori
2011-05-25 11:43                   ` Bastien ROUCARIES
2011-05-11 12:36   ` Anthony Liguori
2011-05-11 12:46     ` Paolo Bonzini
2011-05-11 12:54       ` Stefan Hajnoczi
2011-05-11 13:08     ` Kevin Wolf
2011-05-11 19:12   ` Stefan Weil
2011-05-12  7:59     ` Kevin Wolf
2011-05-12  9:51   ` Jan Kiszka
2011-05-12  9:59     ` Stefan Hajnoczi
2011-05-24 19:54       ` Jamie Lokier
2011-05-12 10:02     ` Kevin Wolf
2011-05-11 10:15 ` [Qemu-devel] [PATCH 2/2] coroutine: add check-coroutine automated tests Stefan Hajnoczi

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=4DDD5073.80601@twiddle.net \
    --to=rth@twiddle.net \
    --cc=aliguori@us.ibm.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@linux.vnet.ibm.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).