All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
Cc: qemu devel <qemu-devel@nongnu.org>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"eddie . dong" <eddie.dong@intel.com>,
	Jason Wang <jasowang@redhat.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [RFC PATCH V2] qemu-char: Fix context for g_source_attach()
Date: Fri, 8 Jul 2016 09:48:23 +0800	[thread overview]
Message-ID: <20160708014823.GA13961@ad.usersys.redhat.com> (raw)
In-Reply-To: <1466592545-9105-1-git-send-email-zhangchen.fnst@cn.fujitsu.com>

On Wed, 06/22 18:49, Zhang Chen wrote:
> We want to poll and handle chardev in another thread
> other than main loop. But qemu_chr_add_handlers() can only
> work for global default context other than thread default context.
> So we use g_source_attach(xx, g_main_context_get_thread_default())
> replace g_source_attach(xx, NULL) to attach g_source.
> Comments from jason.
> 
> Signed-off-by: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
>  io/channel.c | 2 +-
>  qemu-char.c  | 6 +++---
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/io/channel.c b/io/channel.c
> index 692eb17..cd25677 100644
> --- a/io/channel.c
> +++ b/io/channel.c
> @@ -146,7 +146,7 @@ guint qio_channel_add_watch(QIOChannel *ioc,
>  
>      g_source_set_callback(source, (GSourceFunc)func, user_data, notify);
>  
> -    id = g_source_attach(source, NULL);
> +    id = g_source_attach(source, g_main_context_get_thread_default());
>      g_source_unref(source);
>  
>      return id;
> diff --git a/qemu-char.c b/qemu-char.c
> index 84f49ac..4340457 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -859,7 +859,7 @@ static gboolean io_watch_poll_prepare(GSource *source, gint *timeout_)
>          iwp->src = qio_channel_create_watch(
>              iwp->ioc, G_IO_IN | G_IO_ERR | G_IO_HUP | G_IO_NVAL);
>          g_source_set_callback(iwp->src, iwp->fd_read, iwp->opaque, NULL);
> -        g_source_attach(iwp->src, NULL);
> +        g_source_attach(iwp->src, g_main_context_get_thread_default());
>      } else {
>          g_source_destroy(iwp->src);
>          g_source_unref(iwp->src);
> @@ -918,7 +918,7 @@ static guint io_add_watch_poll(QIOChannel *ioc,
>      iwp->fd_read = (GSourceFunc) fd_read;
>      iwp->src = NULL;
>  
> -    tag = g_source_attach(&iwp->parent, NULL);
> +    tag = g_source_attach(&iwp->parent, g_main_context_get_thread_default());
>      g_source_unref(&iwp->parent);
>      return tag;
>  }
> @@ -3982,7 +3982,7 @@ int qemu_chr_fe_add_watch(CharDriverState *s, GIOCondition cond,
>      }
>  
>      g_source_set_callback(src, (GSourceFunc)func, user_data, NULL);
> -    tag = g_source_attach(src, NULL);
> +    tag = g_source_attach(src, g_main_context_get_thread_default());
>      g_source_unref(src);
>  
>      return tag;
> -- 

IIRC this opens a gate for your special thread (COLO compare thread?) to use
QIOChannel.

I think in the long run it is better to think about allowing integrating QIO to
AioContext, to support its usage outside main loop.  Given how opaque GSource
is, I'm not sure how feasible that is, or how useful it will be.  Anyway we
should definitely hear more opinions from Daniel and Paolo.

Fam

  parent reply	other threads:[~2016-07-08  1:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 10:49 [Qemu-devel] [RFC PATCH V2] qemu-char: Fix context for g_source_attach() Zhang Chen
2016-06-29  6:46 ` Zhang Chen
2016-07-08  1:29   ` Zhang Chen
2016-07-08  1:48 ` Fam Zheng [this message]
2016-07-08  2:12   ` Zhang Chen
2016-07-08  8:54   ` Daniel P. Berrange
2016-07-08 14:27     ` Paolo Bonzini
2016-07-11  2:12       ` Zhang Chen
2016-07-18  1:55         ` Zhang Chen
2016-07-18  5:31           ` Jason Wang
2016-07-18  5:43             ` Zhang Chen

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=20160708014823.GA13961@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.