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 v4 2/5] iothread: provide helpers for internal use
Date: Thu, 28 Sep 2017 10:59:55 +0800 [thread overview]
Message-ID: <20170928025958.1420-3-peterx@redhat.com> (raw)
In-Reply-To: <20170928025958.1420-1-peterx@redhat.com>
IOThread is a general framework that contains IO loop environment and a
real thread behind. It's also good to be used internally inside qemu.
Provide some helpers for it to create iothreads to be used internally.
Put all the internal used iothreads into the internal object container.
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
---
include/sysemu/iothread.h | 8 ++++++++
iothread.c | 16 ++++++++++++++++
2 files changed, 24 insertions(+)
diff --git a/include/sysemu/iothread.h b/include/sysemu/iothread.h
index d2985b30ba..b07663f0a1 100644
--- a/include/sysemu/iothread.h
+++ b/include/sysemu/iothread.h
@@ -46,4 +46,12 @@ AioContext *iothread_get_aio_context(IOThread *iothread);
void iothread_stop_all(void);
GMainContext *iothread_get_g_main_context(IOThread *iothread);
+/*
+ * Helpers used to allocate iothreads for internal use. These
+ * iothreads will not be seen by monitor clients when query using
+ * "query-iothreads".
+ */
+IOThread *iothread_create(const char *id, Error **errp);
+void iothread_destroy(IOThread *iothread);
+
#endif /* IOTHREAD_H */
diff --git a/iothread.c b/iothread.c
index 44c8944dc4..33f996e561 100644
--- a/iothread.c
+++ b/iothread.c
@@ -354,3 +354,19 @@ GMainContext *iothread_get_g_main_context(IOThread *iothread)
return iothread->worker_context;
}
+
+IOThread *iothread_create(const char *id, Error **errp)
+{
+ Object *obj;
+
+ obj = object_new_with_props(TYPE_IOTHREAD,
+ object_get_internal_root(),
+ id, errp, NULL);
+
+ return IOTHREAD(obj);
+}
+
+void iothread_destroy(IOThread *iothread)
+{
+ object_unparent(OBJECT(iothread));
+}
--
2.13.5
next prev parent reply other threads:[~2017-09-28 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 2:59 [Qemu-devel] [PATCH v4 0/5] iothread: allow to create internal iothreads Peter Xu
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 1/5] qom: provide root container for internal objs Peter Xu
2017-09-28 7:11 ` Fam Zheng
2017-09-28 2:59 ` Peter Xu [this message]
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 3/5] iothread: export iothread_stop() Peter Xu
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 4/5] iothread: delay the context release to finalize Peter Xu
2017-09-28 2:59 ` [Qemu-devel] [PATCH v4 5/5] aio: fix assert when remove poll during destroy Peter Xu
2017-09-28 7:11 ` Fam Zheng
2017-09-28 9:59 ` Stefan Hajnoczi
2017-09-28 10:28 ` [Qemu-devel] [PATCH v4 0/5] iothread: allow to create internal iothreads 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=20170928025958.1420-3-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).