From: Paolo Bonzini <pbonzini@redhat.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Ping 1.2 PATCH "eventfd: making it thread safe" (was Re: [PATCH v2 1/3] net: asynchronous send/receive infrastructure for net/socket.c)
Date: Tue, 21 Aug 2012 20:54:13 +0200 [thread overview]
Message-ID: <5033D955.5090304@redhat.com> (raw)
In-Reply-To: <CAN05THReyzsSGfa2Ei0ntCPgMe99ewTwODn8S76552PjGto2ng@mail.gmail.com>
Il 21/08/2012 18:39, ronnie sahlberg ha scritto:
> In
> net_socket_update_fd_handler()
>
> shouldnt you call qemu_notify_event() if any of the handlers have
> changed from NULL to non-NULL ?
> or else it might take a while before the change takes effect.
Why haven't we applied yet the patch to do that unconditionally?
http://permalink.gmane.org/gmane.comp.emulators.qemu/162828
Paolo
next prev parent reply other threads:[~2012-08-21 18:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 15:52 [Qemu-devel] [PATCH v2 0/3] net: asynchronous send/receive for net/socket.c Stefan Hajnoczi
2012-08-21 15:52 ` [Qemu-devel] [PATCH v2 1/3] net: asynchronous send/receive infrastructure " Stefan Hajnoczi
2012-08-21 16:39 ` ronnie sahlberg
2012-08-21 18:54 ` Paolo Bonzini [this message]
2012-08-21 19:06 ` [Qemu-devel] Ping 1.2 PATCH "eventfd: making it thread safe" (was Re: [PATCH v2 1/3] net: asynchronous send/receive infrastructure for net/socket.c) Anthony Liguori
2012-08-22 21:07 ` Paolo Bonzini
2012-08-22 21:25 ` Anthony Liguori
2012-08-22 9:24 ` [Qemu-devel] [PATCH v2 1/3] net: asynchronous send/receive infrastructure for net/socket.c Stefan Hajnoczi
2012-08-21 15:52 ` [Qemu-devel] [PATCH v2 2/3] net: EAGAIN handling for net/socket.c UDP Stefan Hajnoczi
2012-08-21 15:52 ` [Qemu-devel] [PATCH v2 3/3] net: EAGAIN handling for net/socket.c TCP Stefan Hajnoczi
2012-08-29 15:35 ` [Qemu-devel] [PATCH v2 0/3] net: asynchronous send/receive for net/socket.c Stefan Hajnoczi
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=5033D955.5090304@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.