From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrange" <berrange@redhat.com>,
"Stefan Hajnoczi" <shajnocz@redhat.com>,
"Fam Zheng" <famz@redhat.com>,
peterx@redhat.com, "Andreas Färber" <afaerber@suse.de>,
"Manos Pitsidianakis" <el13635@mail.ntua.gr>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/4] iothread: allow to create internal iothreads
Date: Tue, 26 Sep 2017 12:52:08 +0800 [thread overview]
Message-ID: <1506401532-25274-1-git-send-email-peterx@redhat.com> (raw)
v3:
- pick up r-bs (one missing for Fam's on last patch)
- fix patch 1 to create isolated internal container
v2:
- add one patch to provide object_get_internal_root() [Daniel]
- patch 2: use the new object_get_internal_root()
- patch 3: fix commit message, "reentrant" is wrongly used by me. it
should be "called multiple times"; move iothread->ctx check into
iothread_stop() [Fam]
- patch 4: add one paragraph in commit message, mention about the glib
issue. [Fam]
When trying to support monitor OOB (out-of-band) commands, I found
that the monitor IO thread I did looks just like iothread. It would
be best if I can use iothread directly. However it seems that it was
mostly used by "-object iothread" before but not friendly to internal
usages. This series tries to export essential functions to do it.
Also, I think patch 2 also fixes a bug in iothread_stop().
Please review. Thanks.
Peter Xu (4):
qom: provide root container for internal objs
iothread: provide helpers for internal use
iothread: export iothread_stop()
iothread: delay the context release to finalize
include/qom/object.h | 10 ++++++++++
include/sysemu/iothread.h | 9 +++++++++
iothread.c | 46 ++++++++++++++++++++++++++++++++++++----------
qom/object.c | 11 +++++++++++
4 files changed, 66 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2017-09-26 4:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 4:52 Peter Xu [this message]
2017-09-26 4:52 ` [Qemu-devel] [PATCH v3 1/4] qom: provide root container for internal objs Peter Xu
2017-09-26 4:58 ` Fam Zheng
2017-09-26 5:12 ` Peter Xu
2017-09-26 8:46 ` Stefan Hajnoczi
2017-09-26 8:49 ` Peter Xu
2017-09-26 4:52 ` [Qemu-devel] [PATCH v3 2/4] iothread: provide helpers for internal use Peter Xu
2017-09-26 4:59 ` Fam Zheng
2017-09-26 8:46 ` Stefan Hajnoczi
2017-09-26 4:52 ` [Qemu-devel] [PATCH v3 3/4] iothread: export iothread_stop() Peter Xu
2017-09-26 4:52 ` [Qemu-devel] [PATCH v3 4/4] iothread: delay the context release to finalize Peter Xu
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=1506401532-25274-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=afaerber@suse.de \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=el13635@mail.ntua.gr \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shajnocz@redhat.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).