All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
	qemu devel <qemu-devel@nongnu.org>
Cc: "eddie . dong" <eddie.dong@intel.com>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH V4 0/4] Introduce COLO-compare
Date: Mon, 20 Jun 2016 13:24:25 +0800	[thread overview]
Message-ID: <57677E09.6090004@redhat.com> (raw)
In-Reply-To: <576762A5.9000906@cn.fujitsu.com>



On 2016年06月20日 11:27, Zhang Chen wrote:
>
>
> On 06/20/2016 11:03 AM, Jason Wang wrote:
>>
>>
>> On 2016年06月17日 10:25, Zhang Chen wrote:
>>> Hi~ jason.
>>>
>>> I tried a lot of ways to make it run in compare thread, but it not 
>>> work.
>>>
>>> Because that:
>>> void g_main_context_push_thread_default (GMainContext *context);
>>> Acquires context and sets it as the thread-default context for the 
>>> current thread.
>>>
>>> So, this function g_main_context_push_thread_default() just can set 
>>> thread-default context,
>>> not the global default context. and I can't find a function to set 
>>> global default context in glib.
>>> The qemu's QIOChannel uses g_source_attach(source, NULL); to attach 
>>> GSource.
>>> g_source_attach (GSource *source,
>>>                  GMainContext *context);
>>>
>>> context
>>> a GMainContext (if NULL, the default context will be used).
>>>
>>> But he not say "the default context" is global default context or 
>>> thread-default context.
>>> So I read glib codes find that:
>>> guint
>>> g_source_attach (GSource *source,
>>>                  GMainContext *context)
>>> {
>>> .....
>>> if (!context)
>>>     context = g_main_context_default ();
>>> .....
>>> }
>>>
>>> g_main_context_default ()
>>> Returns the global default main context.
>>>
>>> So...I think we can't make qemu_chr_add_handlers() run in colo 
>>> thread in this way.
>>> Do you have any comments about that? 
>>
>> How about (like I suggest previously) just use
>>
>> g_souce_attach(x, g_main_context_get_thread_default());
>>
>> in qemu's QIOChannel code?
>>
>>
>>
>
> I feel it seems can work, and will try it.
> but I don't know how this change in qemu's QIOChannel code
> will affect the other code. needs other people confirm it?

Yes, we need convince them. I believe we don't do this in the past is 
because there's no users.

> If no affect and works good,I will send a independent patch
> for this.
>

Right, if it works, please send a RFC and explain why it is needed.

Thanks

>
> Thanks
> Zhang Chen

  reply	other threads:[~2016-06-20  5:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25 12:50 [Qemu-devel] [RFC PATCH V4 0/4] Introduce COLO-compare Zhang Chen
2016-05-25 12:50 ` [Qemu-devel] [RFC PATCH V4 1/4] colo-compare: introduce colo compare initialization Zhang Chen
2016-05-25 12:50 ` [Qemu-devel] [RFC PATCH V4 2/4] colo-compare: track connection and enqueue packet Zhang Chen
2016-05-25 12:50 ` [Qemu-devel] [RFC PATCH V4 3/4] colo-compare: introduce packet comparison thread Zhang Chen
2016-05-25 12:50 ` [Qemu-devel] [RFC PATCH V4 4/4] colo-compare: add TCP, UDP, ICMP packet comparison Zhang Chen
2016-05-30  3:19 ` [Qemu-devel] [RFC PATCH V4 0/4] Introduce COLO-compare Jason Wang
2016-05-31  3:54   ` Zhang Chen
2016-05-31  6:16     ` Jason Wang
2016-05-31  8:28       ` Zhang Chen
2016-05-31 11:06         ` Jason Wang
2016-06-17  2:25           ` Zhang Chen
2016-06-20  3:03             ` Jason Wang
2016-06-20  3:27               ` Zhang Chen
2016-06-20  5:24                 ` Jason Wang [this message]
2016-06-22  6:24                   ` Zhang Chen
2016-06-22  6:48                     ` Jason Wang
2016-06-22  7:10                       ` 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=57677E09.6090004@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --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 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.