From: Stefan Hajnoczi <stefanha@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"Shergill, Gurinder" <gurinder.shergill@hp.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"Vinod, Chegu" <chegu_vinod@hp.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] dataplane: add query-iothreads QMP command
Date: Mon, 3 Mar 2014 10:22:18 +0100 [thread overview]
Message-ID: <20140303092218.GC4780@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20140228140028.16093fee@redhat.com>
On Fri, Feb 28, 2014 at 02:00:28PM -0500, Luiz Capitulino wrote:
> On Thu, 27 Feb 2014 11:48:40 +0100
> Stefan Hajnoczi <stefanha@redhat.com> wrote:
>
> > v3:
> > * Loop until predicate is true to handle pthread_cond spurious wakeups [eblake]
> > * Fix additional instances of "thread_id" [eblake]
> >
> > v2:
> > * Use "thread-id" instead of "thread_id" in QAPI [eblake]
> > * Avoid mutex unlock/destroy race between threads [pbonzini]
> >
> > This series applies on top of "[PATCH v4 0/6] dataplane: switch to N:M
> > devices-per-thread model".
>
> What's the merge plan for both series? IMO, they should go in through the
> block layer tree. As far as the QMP interface is concerned, Eric's review is
> all you need.
Okay, thanks.
They can go through Kevin if he's ready to merge them this week, or me
next week otherwise.
Stefan
next prev parent reply other threads:[~2014-03-03 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 10:48 [Qemu-devel] [PATCH v3 0/2] dataplane: add query-iothreads QMP command Stefan Hajnoczi
2014-02-27 10:48 ` [Qemu-devel] [PATCH v3 1/2] iothread: stash thread ID away Stefan Hajnoczi
2014-02-27 10:48 ` [Qemu-devel] [PATCH v3 2/2] qmp: add query-iothreads command Stefan Hajnoczi
2014-02-27 13:51 ` [Qemu-devel] [PATCH v3 0/2] dataplane: add query-iothreads QMP command Eric Blake
2014-02-28 19:00 ` Luiz Capitulino
2014-03-03 9:22 ` Stefan Hajnoczi [this message]
2014-03-11 18:30 ` 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=20140303092218.GC4780@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=chegu_vinod@hp.com \
--cc=gurinder.shergill@hp.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--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).