qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Wang yong <wang.yong155@zte.com.cn>
Cc: lizhijian@cn.fujitsu.com, zhang.zhanghailiang@huawei.com,
	zhangchen.fnst@cn.fujitsu.com, wang.guang55@zte.com.cn,
	jasowang@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
	pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCHv5 01/03] qemu-iothread: IOThread supports the GMainContext event loop
Date: Thu, 31 Aug 2017 14:45:11 +0800	[thread overview]
Message-ID: <20170831064511.GI17741@lemon.lan> (raw)
In-Reply-To: <20170831021838.GG17741@lemon.lan>

On Thu, 08/31 10:18, Fam Zheng wrote:
> On Tue, 08/29 15:22, Wang yong wrote:
> > From: Wang Yong <wang.yong155@zte.com.cn>
> > 
> > IOThread uses AioContext event loop and does not run a GMainContext.
> > Therefore,chardev cannot work in IOThread,such as the chardev is
> > used for colo-compare packets reception.
> > 
> > This patch makes the IOThread run the GMainContext event loop,
> > chardev and IOThread can work together.
> > 
> > Signed-off-by: Wang Yong <wang.yong155@zte.com.cn>
> > Signed-off-by: Wang Guang <wang.guang55@zte.com.cn>
> > ---
> >  include/sysemu/iothread.h |  4 ++++
> >  iothread.c                | 45 +++++++++++++++++++++++++++++++++++++++++++++
> >  2 files changed, 49 insertions(+)
> > 
> > diff --git a/include/sysemu/iothread.h b/include/sysemu/iothread.h
> > index e6da1a4..d2985b3 100644
> > --- a/include/sysemu/iothread.h
> > +++ b/include/sysemu/iothread.h
> > @@ -24,6 +24,9 @@ typedef struct {
> >  
> >      QemuThread thread;
> >      AioContext *ctx;
> > +    GMainContext *worker_context;
> > +    GMainLoop *main_loop;
> > +    GOnce once;
> >      QemuMutex init_done_lock;
> >      QemuCond init_done_cond;    /* is thread initialization done? */
> >      bool stopping;
> > @@ -41,5 +44,6 @@ typedef struct {
> >  char *iothread_get_id(IOThread *iothread);
> >  AioContext *iothread_get_aio_context(IOThread *iothread);
> >  void iothread_stop_all(void);
> > +GMainContext *iothread_get_g_main_context(IOThread *iothread);
> >  
> >  #endif /* IOTHREAD_H */
> > diff --git a/iothread.c b/iothread.c
> > index beeb870..44c8944 100644
> > --- a/iothread.c
> > +++ b/iothread.c
> > @@ -57,6 +57,23 @@ static void *iothread_run(void *opaque)
> >  
> >      while (!atomic_read(&iothread->stopping)) {
> >          aio_poll(iothread->ctx, true);
> > +
> > +        if (atomic_read(&iothread->worker_context)) {
> > +            GMainLoop *loop;
> > +
> > +            g_main_context_push_thread_default(iothread->worker_context);
> > +            iothread->main_loop =
> > +                g_main_loop_new(iothread->worker_context, TRUE);
> > +            loop = iothread->main_loop;
> > +
> > +            g_main_loop_run(iothread->main_loop);
> > +            iothread->main_loop = NULL;
> > +            g_main_loop_unref(loop);
> > +
> > +            g_main_context_pop_thread_default(iothread->worker_context);
> > +            g_main_context_unref(iothread->worker_context);
> > +            iothread->worker_context = NULL;
> > +        }
> >      }
> >  
> >      rcu_unregister_thread();
> > @@ -73,6 +90,9 @@ static int iothread_stop(Object *object, void *opaque)
> >      }
> >      iothread->stopping = true;
> >      aio_notify(iothread->ctx);
> > +    if (atomic_read(&iothread->main_loop)) {
> > +        g_main_loop_quit(iothread->main_loop);
> > +    }
> >      qemu_thread_join(&iothread->thread);
> >      return 0;
> >  }
> > @@ -125,6 +145,7 @@ static void iothread_complete(UserCreatable *obj, Error **errp)
> >  
> >      qemu_mutex_init(&iothread->init_done_lock);
> >      qemu_cond_init(&iothread->init_done_cond);
> > +    iothread->once = (GOnce) G_ONCE_INIT;
> 
> In last review I suggested removing this type cast, otherwise looks good. Drop
> it and please add

No, Yong is right, because this is not varialble initializer, type cast is
required by C. Sorry for the noise.

Fam

  reply	other threads:[~2017-08-31  6:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  7:22 [Qemu-devel] [PATCHv5 00/03] Replace the COLO comparing thread with IOThread Wang yong
2017-08-29  7:22 ` [Qemu-devel] [PATCHv5 01/03] qemu-iothread: IOThread supports the GMainContext event loop Wang yong
2017-08-31  2:18   ` Fam Zheng
2017-08-31  6:45     ` Fam Zheng [this message]
2017-08-31 10:13   ` Stefan Hajnoczi
2017-08-29  7:22 ` [Qemu-devel] [PATCHv5 02/03] colo-compare: Use IOThread to Check old packet regularly and Process pactkets of the primary Wang yong
2017-09-07  3:22   ` Zhang Chen
2017-08-29  7:22 ` [Qemu-devel] [PATCHv5 03/03] colo-compare: Update the COLO document to add the IOThread configuration Wang yong
2017-09-07  3:23   ` Zhang Chen
2017-09-08  1:32 ` [Qemu-devel] [PATCHv5 00/03] Replace the COLO comparing thread with IOThread Jason Wang

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=20170831064511.GI17741@lemon.lan \
    --to=famz@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wang.guang55@zte.com.cn \
    --cc=wang.yong155@zte.com.cn \
    --cc=zhang.zhanghailiang@huawei.com \
    --cc=zhangchen.fnst@cn.fujitsu.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).