From: Juan Quintela <quintela@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Le Tan <tamlokveer@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to understand the coroutine context?
Date: Tue, 18 Mar 2014 14:13:03 +0100 [thread overview]
Message-ID: <87ppljps4g.fsf@elfo.mitica> (raw)
In-Reply-To: <87iorbll9i.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Tue, 18 Mar 2014 13:54:49 +0100")
Markus Armbruster <armbru@redhat.com> wrote:
> Juan Quintela <quintela@redhat.com> writes:
>
>> Le Tan <tamlokveer@gmail.com> 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!
>>
>> google, 1st hit, wikipedia:
>>
>> https://en.wikipedia.org/wiki/Coroutine
>>
>> A bit short resume:
>>
>> Getting "user"-threads when you don't have threads.
>
> More like getting multiple flows of control even though you don't want
> threads.
If he don't understand coroutine, you think that flows of control has
any chance? O:-)
Later, Juan.
next prev parent reply other threads:[~2014-03-18 13:13 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
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 [this message]
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=87ppljps4g.fsf@elfo.mitica \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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.