qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kwolf@redhat.com, sheepdog@lists.wpkg.org, qemu-devel@nongnu.org,
	MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] coroutine bug?, was Re: [PATCH] sheepdog: use coroutines
Date: Tue, 3 Jan 2012 08:16:55 +0000	[thread overview]
Message-ID: <20120103081655.GB28636@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20120102153959.GA22823@lst.de>

On Mon, Jan 02, 2012 at 04:39:59PM +0100, Christoph Hellwig wrote:
> I've tried to understand how the recursive calling happens, but unfortunately
> the whole coroutine code lacks any sort of documentation how it should
> behave or what it asserts about the callers.

There is documentation on the public coroutine functions, see
qemu-coroutine.h.

If you have specific questions I can improve the documentation.  Please
let me know.

Stefan

  parent reply	other threads:[~2012-01-03  9:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-12 12:33 [Qemu-devel] [PATCH] sheepdog: use coroutines MORITA Kazutaka
2011-08-23 12:29 ` Kevin Wolf
2011-08-23 17:14   ` MORITA Kazutaka
2011-08-24 12:56     ` Kevin Wolf
2011-12-23 13:38 ` Christoph Hellwig
2011-12-29 12:06   ` [Qemu-devel] coroutine bug?, was " Christoph Hellwig
2011-12-30 10:35     ` Stefan Hajnoczi
2012-01-02 15:39       ` Christoph Hellwig
2012-01-02 15:40         ` Christoph Hellwig
2012-01-02 22:38         ` Stefan Hajnoczi
2012-01-03  8:13           ` Stefan Hajnoczi
2012-01-06 11:16             ` MORITA Kazutaka
2012-01-03  8:16         ` Stefan Hajnoczi [this message]
2012-01-04 15:58           ` Christoph Hellwig
2012-01-04 17:03             ` Paolo Bonzini

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=20120103081655.GB28636@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=hch@lst.de \
    --cc=kwolf@redhat.com \
    --cc=morita.kazutaka@lab.ntt.co.jp \
    --cc=qemu-devel@nongnu.org \
    --cc=sheepdog@lists.wpkg.org \
    /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).