qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Fam Zheng <famz@redhat.com>
Cc: "eddie . dong" <eddie.dong@intel.com>,
	qemu devel <qemu-devel@nongnu.org>,
	Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [RFC PATCH V2] qemu-char: Fix context for g_source_attach()
Date: Mon, 18 Jul 2016 13:31:35 +0800	[thread overview]
Message-ID: <578C69B7.2010707@redhat.com> (raw)
In-Reply-To: <578C370B.8020302@cn.fujitsu.com>



On 2016年07月18日 09:55, Zhang Chen wrote:
> Hi~ All~~
>
> Can you give me some feedback for this patch?
>
> We need more comments~~
>
> COLO project depend on this patch to work.
>
> Because this patch colo-compare can make handler of 
> qemu_chr_add_handlers()
>
> run in compare thread, reduce workload of main_loop in network busy 
> situation.
>
> This idea from Jason.
>
>
> Thanks
> Zhang Chen

I think you can put this patch in the series of COLO comparing thread 
which shows its using. And then you can ask acked-by or reviewed-by from 
other maintainers.

Thanks

  reply	other threads:[~2016-07-18  5:31 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
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 [this message]
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=578C69B7.2010707@redhat.com \
    --to=jasowang@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=famz@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 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).