qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: wang.yong155@zte.com.cn, zhang.zhanghailiang@huawei.com,
	zhangchen.fnst@cn.fujitsu.com, lizhijian@cn.fujitsu.com,
	qemu-devel@nongnu.org, wang.guang55@zte.com.cn,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>
Subject: Re: [Qemu-devel] 答复: Re: 答复: Re: [PATCHv2 02/04] colo-compare: Process pactkets in the IOThread ofthe primary
Date: Fri, 16 Jun 2017 10:20:04 +0100	[thread overview]
Message-ID: <20170616092004.GF31462@stefanha-x1.localdomain> (raw)
In-Reply-To: <d62e03ee-f3ab-303e-011d-8b995530b6ab@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 523 bytes --]

On Thu, Jun 15, 2017 at 12:23:27PM +0800, Jason Wang wrote:
> Paolo, Marc and Stefan:
> 
> We want let chardev front-end run in colo comparing IOThread. This looks not
> supported by current chardev frontend API. Any idea/suggestion on how to
> achieve this?

A follow-up:

I just noticed that io/ supports AioContext.

This means a different approach is to add AioContext support to the
chardev API so that either GMainContext or AioContext can be used.

Again, I'm not sure how feasible this is.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  parent reply	other threads:[~2017-06-16  9:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 11:24 [Qemu-devel] 答复: Re: 答复: Re: [PATCHv2 02/04] colo-compare: Process pactkets in the IOThread ofthe primary wang.yong155
2017-06-15  4:23 ` Jason Wang
2017-06-16  9:02   ` Stefan Hajnoczi
2017-06-16  9:20   ` Stefan Hajnoczi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-13  0:48 wang.yong155

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=20170616092004.GF31462@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).