From: Christoph Hellwig <hch@lst.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, sheepdog@lists.wpkg.org,
Christoph Hellwig <hch@lst.de>,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] coroutine bug?, was Re: [PATCH] sheepdog: use coroutines
Date: Wed, 4 Jan 2012 16:58:25 +0100 [thread overview]
Message-ID: <20120104155825.GA11210@lst.de> (raw)
In-Reply-To: <20120103081655.GB28636@stefanha-thinkpad.localdomain>
On Tue, Jan 03, 2012 at 08:16:55AM +0000, Stefan Hajnoczi wrote:
> 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.
Ok, I was looking in the source files and the documentation directory only
as that is where I expected the documentation to sit.
Btw, what is the plan forward for the block I/O interface? Only
qcow2, sheepdog and nbd implement the coroutine interfaces, and none of the
hardware emulations calls them directly. Also at least for interfaces
like the librbd callbacks coroutines don't even seem to be that useful.
next prev parent reply other threads:[~2012-01-04 15:58 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
2012-01-04 15:58 ` Christoph Hellwig [this message]
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=20120104155825.GA11210@lst.de \
--to=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.org \
--cc=stefanha@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).