qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] coroutine: introduce coroutines
Date: Thu, 12 May 2011 11:51:32 +0200	[thread overview]
Message-ID: <4DCBADA4.6030401@siemens.com> (raw)
In-Reply-To: <1305108925-26048-2-git-send-email-stefanha@linux.vnet.ibm.com>

On 2011-05-11 12:15, Stefan Hajnoczi wrote:
> From: Kevin Wolf <kwolf@redhat.com>
> 
> Asynchronous code is becoming very complex.  At the same time
> synchronous code is growing because it is convenient to write.
> Sometimes duplicate code paths are even added, one synchronous and the
> other asynchronous.  This patch introduces coroutines which allow code
> that looks synchronous but is asynchronous under the covers.
> 
> A coroutine has its own stack and is therefore able to preserve state
> across blocking operations, which traditionally require callback
> functions and manual marshalling of parameters.
> 
> Creating and starting a coroutine is easy:
> 
>   coroutine = qemu_coroutine_create(my_coroutine);
>   qemu_coroutine_enter(coroutine, my_data);
> 
> The coroutine then executes until it returns or yields:
> 
>   void coroutine_fn my_coroutine(void *opaque) {
>       MyData *my_data = opaque;
> 
>       /* do some work */
> 
>       qemu_coroutine_yield();
> 
>       /* do some more work */
>   }
> 
> Yielding switches control back to the caller of qemu_coroutine_enter().
> This is typically used to switch back to the main thread's event loop
> after issuing an asynchronous I/O request.  The request callback will
> then invoke qemu_coroutine_enter() once more to switch back to the
> coroutine.
> 
> Note that coroutines never execute concurrently and should only be used
> from threads which hold the global mutex.  This restriction makes
> programming with coroutines easier than with threads.  Race conditions
> cannot occur since only one coroutine may be active at any time.  Other
> coroutines can only run across yield.

Mmh, is there anything that conceptually prevent fixing this limitation
later on? I would really like to remove such dependency long-term as
well to have VCPUs operate truly independently on independent device models.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2011-05-12  9:51 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
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 [this message]
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=4DCBADA4.6030401@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).