From: Stefan Hajnoczi <stefanha@redhat.com>
To: liu ping fan <qemulist@gmail.com>
Cc: mdroth <mdroth@linux.vnet.ibm.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH v5 01/14] util: introduce gsource event abstraction
Date: Mon, 29 Apr 2013 10:00:56 +0200 [thread overview]
Message-ID: <20130429080056.GC13488@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAJnKYQmAkSsspiL5chzFLnMkdbSM7nhC5wKKL1MzZkz7Oz53WQ@mail.gmail.com>
On Sat, Apr 27, 2013 at 10:11:40AM +0800, liu ping fan wrote:
> On Fri, Apr 26, 2013 at 5:19 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > On Fri, Apr 26, 2013 at 10:47:22AM +0800, Liu Ping Fan wrote:
> >> +GPollFD *events_source_add_gfd(EventsGSource *src, int fd)
> >> +{
> >> + GPollFD *retfd;
> >> +
> >> + retfd = g_slice_alloc(sizeof(GPollFD));
> >> + retfd->events = 0;
> >> + retfd->fd = fd;
> >> + src->pollfds_list = g_list_append(src->pollfds_list, retfd);
> >> + if (fd > 0) {
> >
> > 0 (stdin) is a valid fd number. Maybe just assert(fd >= 0)?
> >
> Yes, 0 should be allowed. Here, the reason to use check instead of
> assert , is that socreate() in slirp is a good place to call
> _add_gfd, but unfortunately, at that time, its socket handler so->s =
> -1; So we create the GPollFD ahead, and delay to call
> g_source_add_poll()
ok
> >> +static gboolean events_source_check(GSource *src)
> >> +{
> >> + EventsGSource *nsrc = (EventsGSource *)src;
> >> + GList *cur;
> >> + GPollFD *gfd;
> >> +
> >> + cur = nsrc->pollfds_list;
> >> + while (cur) {
> >> + gfd = cur->data;
> >> + if (gfd->fd > 0 && (gfd->revents & gfd->events)) {
> >
> > revents will always be 0 if fd is invalid, since we didn't call
> > g_source_add_poll(). Is there a reason to perform the fd > 0 check
> > again?
> >
> As explained above, we should skip the case gfd->fd=-1, which may
> occur in pollfds_list.
ok
> >> +void events_source_release(EventsGSource *src)
> >> +{
> >
> > assert that pollfds_list is empty? We don't g_slice_free() GPollFDs so
> > it must be empty here.
>
> Do you mean that events_source_add_gfd/events_source_remove_gfd are
> paired, so here, we ensure that pollfds_list==NULL ?
Yes. It is an error to hold a GPollFD across events_source_release() so
you could place an assert() here to check.
Stefan
next prev parent reply other threads:[~2013-04-29 8:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 2:47 [Qemu-devel] [RFC PATCH v5 00/14] port network layer onto glib Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 01/14] util: introduce gsource event abstraction Liu Ping Fan
2013-04-26 9:19 ` Stefan Hajnoczi
2013-04-27 2:11 ` liu ping fan
2013-04-29 8:00 ` Stefan Hajnoczi [this message]
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 02/14] net: introduce bind_ctx to NetClientInfo Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 03/14] net: port tap onto GSource Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 04/14] net: port vde " Liu Ping Fan
2013-04-26 9:25 ` Stefan Hajnoczi
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 05/14] net: port socket to GSource Liu Ping Fan
2013-04-26 9:48 ` Stefan Hajnoczi
2013-04-27 7:09 ` liu ping fan
2013-04-29 8:21 ` Stefan Hajnoczi
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 06/14] net: port tap-win32 onto GSource Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 07/14] net: hub use lock to protect ports list Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 08/14] net: introduce lock to protect NetQueue Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 09/14] net: introduce lock to protect NetClientState's peer's access Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 10/14] net: make netclient re-entrant with refcnt Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 11/14] slirp: make timeout local Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 12/14] slirp: make slirp event dispatch based on slirp instance, not global Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 13/14] slirp: handle race condition Liu Ping Fan
2013-04-26 2:47 ` [Qemu-devel] [RFC PATCH v5 14/14] slirp: use lock to protect the slirp_instances Liu Ping Fan
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=20130429080056.GC13488@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.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).