qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, peter.crosthwaite@xilinx.com
Subject: Re: [Qemu-devel] [PATCH] qemu-char: really fix behavior on can_read = 0
Date: Mon, 08 Apr 2013 08:56:01 -0500	[thread overview]
Message-ID: <87a9p9gm8e.fsf@codemonkey.ws> (raw)
In-Reply-To: <1365426195-12596-1-git-send-email-pbonzini@redhat.com>

Paolo Bonzini <pbonzini@redhat.com> writes:

> I misread the glib manual, g_source_remove does not let you re-attach
> the source later.  This behavior (called "blocking" the source in glib)
> is present in glib's source code, but private and not available outside
> glib; hence, we have to resort to re-creating the source every time.
>
> In fact, g_source_remove and g_source_destroy are the same thing,
> except g_source_destroy is O(1) while g_source_remove scans a potentially
> very long list of GSources in the current main loop.  Ugh.  Better
> use g_source_destroy explicitly, and leave "tags" to those dummies who
> cannot track their pointers' lifetimes.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

Tested-by: Anthony Liguori <aliguori@us.ibm.com>

Regards,

Anthony Liguori

> ---
>  qemu-char.c | 17 +++++++++++++----
>  1 file changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index dd410ce..eae17fc 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -596,9 +596,11 @@ typedef struct IOWatchPoll
>  {
>      GSource parent;
>  
> +    GIOChannel *channel;
>      GSource *src;
>  
>      IOCanReadHandler *fd_can_read;
> +    GSourceFunc fd_read;
>      void *opaque;
>  } IOWatchPoll;
>  
> @@ -611,15 +613,19 @@ static gboolean io_watch_poll_prepare(GSource *source, gint *timeout_)
>  {
>      IOWatchPoll *iwp = io_watch_poll_from_source(source);
>      bool now_active = iwp->fd_can_read(iwp->opaque) > 0;
> -    bool was_active = g_source_get_context(iwp->src) != NULL;
> +    bool was_active = iwp->src != NULL;
>      if (was_active == now_active) {
>          return FALSE;
>      }
>  
>      if (now_active) {
> +        iwp->src = g_io_create_watch(iwp->channel, G_IO_IN | G_IO_ERR | G_IO_HUP);
> +        g_source_set_callback(iwp->src, iwp->fd_read, iwp->opaque, NULL);
>          g_source_attach(iwp->src, NULL);
>      } else {
> -        g_source_remove(g_source_get_id(iwp->src));
> +        g_source_destroy(iwp->src);
> +        g_source_unref(iwp->src);
> +        iwp->src = NULL;
>      }
>      return FALSE;
>  }
> @@ -638,7 +644,9 @@ static gboolean io_watch_poll_dispatch(GSource *source, GSourceFunc callback,
>  static void io_watch_poll_finalize(GSource *source)
>  {
>      IOWatchPoll *iwp = io_watch_poll_from_source(source);
> +    g_source_destroy(iwp->src);
>      g_source_unref(iwp->src);
> +    iwp->src = NULL;
>  }
>  
>  static GSourceFuncs io_watch_poll_funcs = {
> @@ -659,8 +667,9 @@ static guint io_add_watch_poll(GIOChannel *channel,
>      iwp = (IOWatchPoll *) g_source_new(&io_watch_poll_funcs, sizeof(IOWatchPoll));
>      iwp->fd_can_read = fd_can_read;
>      iwp->opaque = user_data;
> -    iwp->src = g_io_create_watch(channel, G_IO_IN | G_IO_ERR | G_IO_HUP);
> -    g_source_set_callback(iwp->src, (GSourceFunc)fd_read, user_data, NULL);
> +    iwp->channel = channel;
> +    iwp->fd_read = (GSourceFunc) fd_read;
> +    iwp->src = NULL;
>  
>      return g_source_attach(&iwp->parent, NULL);
>  }
> -- 
> 1.8.1.4

  reply	other threads:[~2013-04-08 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 13:03 [Qemu-devel] [PATCH] qemu-char: really fix behavior on can_read = 0 Paolo Bonzini
2013-04-08 13:56 ` Anthony Liguori [this message]
2013-04-08 14:08 ` Hans de Goede
2013-04-08 14:08   ` Paolo Bonzini
2013-04-08 21:55 ` Anthony Liguori

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=87a9p9gm8e.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=amit.shah@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    /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).