qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] chardev: convert leftover glib APIs to use dedicate gcontext
Date: Wed, 3 Jan 2018 16:54:21 +0800	[thread overview]
Message-ID: <20180103085421.GC2557@xz-mi> (raw)
In-Reply-To: <cd7d1d86-331f-1a0e-2a39-bee1d536157b@redhat.com>

On Wed, Jan 03, 2018 at 08:10:58AM +0100, Paolo Bonzini wrote:
> On 28/12/2017 08:29, Peter Xu wrote:
> > There were existing work that tried to allow chardev to be run in a
> > dedicated gcontext rather than the default main context/thread.
> > Basically that work passed in the correct gcontext during
> > g_source_attach().  However, I found something missing along the way,
> > that some legacy glib APIs are used by chardev code which take the
> > main context as default:
> > 
> >    g_timeout_add_seconds
> >    g_timeout_add
> >    g_idle_add
> > 
> > To fully allow the chardevs to be run in dedicated gcontext, we need
> > to convert all these legacy APIs into g_source_attach() calls as well,
> > with the correct gcontext passed in.
> > 
> > This series tries to clean the rest of things up.
> > 
> > I picked up patch 1 from monitor-oob series into this series (which is
> > a missing of chardev frontend call fix for g_source_attach()), so that
> > this series can be a complete fix.
> > 
> > Please review.  Thanks,
> > 
> > Peter Xu (3):
> >   chardev: use backend chr context when watch for fe
> >   chardev: let g_idle_add() be with chardev gcontext
> >   chardev: introduce qemu_chr_timeout_add() and use
> > 
> >  chardev/char-fe.c      |  2 +-
> >  chardev/char-pty.c     | 16 ++++++++--------
> >  chardev/char-socket.c  |  4 ++--
> >  chardev/char.c         | 20 ++++++++++++++++++++
> >  hw/char/terminal3270.c |  7 ++++---
> >  include/chardev/char.h |  2 ++
> >  6 files changed, 37 insertions(+), 14 deletions(-)
> > 
> 
> All queued, thanks!

Paolo,

Would you like to queue V2 of the series which fixed the issue that
Marc-Andre has pointed out (Note that there is a v2.1 for patch 3).

Thanks anyways!

-- 
Peter Xu

      reply	other threads:[~2018-01-03  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28  7:29 [Qemu-devel] [PATCH 0/3] chardev: convert leftover glib APIs to use dedicate gcontext Peter Xu
2017-12-28  7:29 ` [Qemu-devel] [PATCH 1/3] chardev: use backend chr context when watch for fe Peter Xu
2018-01-02 16:02   ` Marc-André Lureau
2017-12-28  7:29 ` [Qemu-devel] [PATCH 2/3] chardev: let g_idle_add() be with chardev gcontext Peter Xu
2018-01-02 16:02   ` Marc-André Lureau
2017-12-28  7:29 ` [Qemu-devel] [PATCH 3/3] chardev: introduce qemu_chr_timeout_add() and use Peter Xu
2018-01-02 16:10   ` Marc-André Lureau
2018-01-03  2:06     ` Peter Xu
2018-01-03  7:10 ` [Qemu-devel] [PATCH 0/3] chardev: convert leftover glib APIs to use dedicate gcontext Paolo Bonzini
2018-01-03  8:54   ` Peter Xu [this message]

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=20180103085421.GC2557@xz-mi \
    --to=peterx@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).