From: Stefan Hajnoczi <stefanha@gmail.com>
To: Yaodong Yang <yaodong.yangy@icloud.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] About coroutine inside qemu
Date: Mon, 2 Sep 2013 11:11:40 +0200 [thread overview]
Message-ID: <20130902091140.GB947@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <4f4a2022-68e7-4fc4-aaaf-f14205d3ab0f@me.com>
On Fri, Aug 30, 2013 at 08:59:37PM +0000, Yaodong Yang wrote:
> When a new work thread, which is not inside coroutine, enter a
> coroutine(named as A), what happened to the work thread? Is it true
> that the work thread also become a coroutine, or it just stop? Later
> if the coroutine A call yield. what happened to the work thread?
qemu_coroutine_enter() returns when the coroutine yields or terminates.
Therefore the thread gives its control to the coroutine until it yields
or terminates.
Stefan
prev parent reply other threads:[~2013-09-02 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 20:59 [Qemu-devel] About coroutine inside qemu Yaodong Yang
2013-09-02 9:11 ` Stefan Hajnoczi [this message]
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=20130902091140.GB947@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=yaodong.yangy@icloud.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).