From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Shergill, Gurinder" <gurinder.shergill@hp.com>,
"Vinod, Chegu" <chegu_vinod@hp.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] coroutine: dataplane support
Date: Tue, 21 May 2013 10:15:00 +0200 [thread overview]
Message-ID: <20130521081500.GD30951@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <CAFEAcA8sTF2emrhboAuB8S8OBkTmyRzqkO=9HRo59JrNK_4ZLA@mail.gmail.com>
On Fri, May 17, 2013 at 04:08:36PM +0100, Peter Maydell wrote:
> On 17 May 2013 14:51, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > There is ongoing work to enable multiple event loop threads. This will allow
> > QEMU itself to take advantage of SMP and reduce Big QEMU Lock (BQL) contention.
> > This series is one step in that effort.
> >
> > These patches make coroutines safe in a multi-event loop/multi-threaded world.
> > I have successfully tested them running qcow2 in a dataplane thread (further
> > patches are required which I'll be sending soon).
>
> Did you test the sigaltstack backend as well as ucontext? I know
> in theory they should be the same but still :-)
Yes, I have tested sigaltstack successfully with make check and
qemu-iotests.
Stefan
next prev parent reply other threads:[~2013-05-21 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 13:51 [Qemu-devel] [PATCH 0/2] coroutine: dataplane support Stefan Hajnoczi
2013-05-17 13:51 ` [Qemu-devel] [PATCH 1/2] coroutine: protect global pool with a mutex Stefan Hajnoczi
2013-05-17 13:51 ` [Qemu-devel] [PATCH 2/2] coroutine: stop using AioContext in CoQueue Stefan Hajnoczi
2013-05-17 15:02 ` [Qemu-devel] [PATCH 0/2] coroutine: dataplane support Kevin Wolf
2013-05-17 15:08 ` Peter Maydell
2013-05-21 8:15 ` Stefan Hajnoczi [this message]
2013-05-23 11:58 ` Stefan Hajnoczi
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=20130521081500.GD30951@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=gurinder.shergill@hp.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).