From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <shajnocz@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] iothread: provide helpers for internal use
Date: Sun, 8 Oct 2017 20:46:14 +0800 [thread overview]
Message-ID: <20171008124614.GA7792@pxdev.xzpeter.org> (raw)
In-Reply-To: <87h8vh1nar.fsf@dusky.pond.sub.org>
On Mon, Oct 02, 2017 at 07:18:04PM +0200, Markus Armbruster wrote:
> Stefan Hajnoczi <stefanha@redhat.com> writes:
>
> > On Fri, Sep 22, 2017 at 04:56:10PM +0800, Peter Xu wrote:
> >> 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.
> >>
> >> Signed-off-by: Peter Xu <peterx@redhat.com>
> >> ---
> >> include/sysemu/iothread.h | 8 ++++++++
> >> iothread.c | 21 +++++++++++++++++++++
> >> 2 files changed, 29 insertions(+)
> >>
> >> diff --git a/include/sysemu/iothread.h b/include/sysemu/iothread.h
> >> index d2985b3..b07663f 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 44c8944..74e400c 100644
> >> --- a/iothread.c
> >> +++ b/iothread.c
> >> @@ -354,3 +354,24 @@ GMainContext *iothread_get_g_main_context(IOThread *iothread)
> >>
> >> return iothread->worker_context;
> >> }
> >> +
> >> +static Object *iothread_get_internal_parent(void)
> >> +{
> >> + return container_get(object_get_root(), "/internal-iothreads");
> >> +}
> >
> > Markus, please advise on the following QMP API design issue.
>
> Sorry for the slow response. Is my advice still needed, or are you
> good?
I see that the patches are in master now (latest version, not this
one), and the consensus should be that internally used iothreads won't
affect results of query-iothreads. So I think we are good now. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2017-10-08 12:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 8:56 [Qemu-devel] [PATCH 0/3] iothread: allow to create internal iothreads Peter Xu
2017-09-22 8:56 ` [Qemu-devel] [PATCH 1/3] iothread: provide helpers for internal use Peter Xu
2017-09-22 9:04 ` Daniel P. Berrange
2017-09-22 9:14 ` Peter Xu
2017-09-22 9:36 ` Daniel P. Berrange
2017-09-22 9:38 ` Paolo Bonzini
2017-09-22 9:43 ` Daniel P. Berrange
2017-09-22 10:14 ` Paolo Bonzini
2017-09-22 10:17 ` Daniel P. Berrange
2017-09-22 12:59 ` Fam Zheng
2017-09-22 13:03 ` Paolo Bonzini
2017-09-22 10:54 ` Peter Xu
2017-09-22 10:16 ` Stefan Hajnoczi
2017-09-22 10:18 ` Paolo Bonzini
2017-09-22 10:20 ` Daniel P. Berrange
2017-09-22 10:26 ` Paolo Bonzini
2017-09-22 10:28 ` Daniel P. Berrange
2017-09-22 14:35 ` Stefan Hajnoczi
2017-09-22 14:55 ` Daniel P. Berrange
2017-10-02 17:18 ` Markus Armbruster
2017-10-08 12:46 ` Peter Xu [this message]
2017-09-22 8:56 ` [Qemu-devel] [PATCH 2/3] iothread: export iothread_stop() Peter Xu
2017-09-22 13:06 ` Fam Zheng
2017-09-25 3:29 ` Peter Xu
2017-09-22 8:56 ` [Qemu-devel] [PATCH 3/3] iothread: delay the context release to finalize Peter Xu
2017-09-22 13:09 ` Fam Zheng
2017-09-25 5:23 ` Peter Xu
2017-09-25 5:30 ` Fam Zheng
2017-09-25 5:50 ` Peter Xu
2017-09-25 5:58 ` Fam Zheng
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=20171008124614.GA7792@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shajnocz@redhat.com \
--cc=stefanha@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).