From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51732)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1WPtXq-0000qH-H0
	for qemu-devel@nongnu.org; Tue, 18 Mar 2014 08:55:07 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1WPtXl-0003Rs-6e
	for qemu-devel@nongnu.org; Tue, 18 Mar 2014 08:55:02 -0400
Received: from mx1.redhat.com ([209.132.183.28]:4758)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1WPtXk-0003Ro-VS
	for qemu-devel@nongnu.org; Tue, 18 Mar 2014 08:54:57 -0400
From: Markus Armbruster <armbru@redhat.com>
References: <CACrq+iLGpizO2NH2cf_sschkwZJE3xpeHF-QftrWF=c_4skNig@mail.gmail.com>
	<877g7rr8r0.fsf@elfo.mitica>
Date: Tue, 18 Mar 2014 13:54:49 +0100
In-Reply-To: <877g7rr8r0.fsf@elfo.mitica> (Juan Quintela's message of "Tue, 18
	Mar 2014 13:28:35 +0100")
Message-ID: <87iorbll9i.fsf@blackfin.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Qemu-devel] How to understand the coroutine context?
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: quintela@redhat.com
Cc: Le Tan <tamlokveer@gmail.com>, qemu-devel@nongnu.org

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.