qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: kwolf@redhat.com, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-coroutine: Add simple work queue support
Date: Thu, 25 Aug 2011 09:06:57 +0100	[thread overview]
Message-ID: <20110825080657.GA7046@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <CAEgOgz7jWNRS+ALYWjTaN+0JZjP9GjyyaY55UuDXBbXhfeRo9w@mail.gmail.com>

On Thu, Aug 25, 2011 at 04:46:59PM +1000, Peter Crosthwaite wrote:
> Hi Stefan,
> 
> I have ccd you on a RFC containing the work that this patch uses. I have
> also changed the name of the function to co_queue_enter_next() as i think
> yield was not the appropriate name. The idea is the top level thread which
> is managing the work queue can transfer into coroutine context with the
> function, so this function is more of an "enter" function than a "yield"
> function. I cant see any technical reasons why it needs the coroutine_fn
> restriction, as this in not required by qemu_coroutine_enter, which is the
> backend of this function.

You are right, I was confused by the "yield" in the name :).  It doesn't
need to be coroutine_fn.

Stefan

  reply	other threads:[~2011-08-25  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  7:57 [Qemu-devel] [PATCH] qemu-coroutine: Add simple work queue support Peter A. G. Crosthwaite
2011-08-24 12:08 ` Stefan Hajnoczi
2011-08-25  6:46   ` Peter Crosthwaite
2011-08-25  8:06     ` Stefan Hajnoczi [this message]
2011-09-05 13:23 ` Kevin Wolf

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=20110825080657.GA7046@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=peter.crosthwaite@petalogix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).