From: Thomas Huth <thuth@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Le Tan <tamlokveer@gmail.com>,
Kashyap Chamarthy <kchamart@redhat.com>
Subject: Re: [Qemu-devel] How to understand the coroutine context?
Date: Tue, 18 Mar 2014 23:28:47 +0100 [thread overview]
Message-ID: <20140318232847.16a1e21e@oc7435384737.ibm.com> (raw)
In-Reply-To: <20140318040456.GA13112@tesla.pnq.redhat.com>
On Tue, 18 Mar 2014 09:34:56 +0530
Kashyap Chamarthy <kchamart@redhat.com> wrote:
> On Tue, Mar 18, 2014 at 07:56:16AM +0800, Le Tan wrote:
> > Hi, I am diving into the source code of qemu. I see the word
> > "coroutine" appears in so many places. I can't figure out what it
> > means. So, please, can anyone help me, telling me the mechanism or
> > semantic of "coroutine"? Thanks!
>
> This might be of help --
> http://blog.vmsplice.net/2014/01/coroutines-in-qemu-basics.html
That's a very nice introduction ... Stefan, maybe you could also add
that to the docs directory of the QEMU repository? There does not seem
to be a description of the QEMU coroutines there yet...
Regards,
Thomas
next prev parent reply other threads:[~2014-03-18 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 23:56 [Qemu-devel] How to understand the coroutine context? Le Tan
2014-03-18 4:04 ` Kashyap Chamarthy
2014-03-18 5:45 ` Le Tan
2014-03-18 22:28 ` Thomas Huth [this message]
2014-03-19 10:05 ` Stefan Hajnoczi
2014-03-19 10:13 ` Thomas Huth
2014-03-19 11:15 ` Stefan Hajnoczi
2014-03-18 12:28 ` Juan Quintela
2014-03-18 12:54 ` Markus Armbruster
2014-03-18 13:13 ` Juan Quintela
2014-03-18 13:48 ` Markus Armbruster
2014-03-18 13:57 ` Leandro Dorileo
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=20140318232847.16a1e21e@oc7435384737.ibm.com \
--to=thuth@linux.vnet.ibm.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=tamlokveer@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 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).