From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aliguori@linux.vnet.ibm.com, ryanh@us.ibm.com,
agl@linux.vnet.ibm.com, mdroth@linux.vnet.ibm.com,
abeekhof@redhat.com
Subject: [Qemu-devel] [RFC][PATCH 05/15] virtproxy: add accept handler for communication channel
Date: Fri, 22 Oct 2010 13:43:21 -0500 [thread overview]
Message-ID: <1287773011-24726-6-git-send-email-mdroth@linux.vnet.ibm.com> (raw)
In-Reply-To: <1287773011-24726-1-git-send-email-mdroth@linux.vnet.ibm.com>
This accept()'s connections to the socket we told virt-proxy to listen
for the channel connection on and sets the appropriate read handler for
the resulting FD.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
---
virtproxy.c | 37 +++++++++++++++++++++++++++++++++++++
1 files changed, 37 insertions(+), 0 deletions(-)
diff --git a/virtproxy.c b/virtproxy.c
index fa17722..20532c2 100644
--- a/virtproxy.c
+++ b/virtproxy.c
@@ -166,6 +166,8 @@ static VPConn *get_conn(const VPDriver *drv, int fd, bool client)
return NULL;
}
+static void vp_channel_accept(void *opaque);
+
/* get VPOForward by service_id */
static VPOForward *get_oforward(const VPDriver *drv, const char *service_id)
{
@@ -193,3 +195,38 @@ static VPIForward *get_iforward(const VPDriver *drv, const char *service_id)
return NULL;
}
+
+/* accept handler for communication channel
+ *
+ * accept()s connection to communication channel (for sockets), and sets
+ * up the read handler for resulting FD.
+ */
+static void vp_channel_accept(void *opaque)
+{
+ VPDriver *drv = opaque;
+ struct sockaddr_in saddr;
+ struct sockaddr *addr;
+ socklen_t len;
+ int fd;
+
+ TRACE("called with opaque: %p", drv);
+
+ for(;;) {
+ len = sizeof(saddr);
+ addr = (struct sockaddr *)&saddr;
+ fd = qemu_accept(drv->listen_fd, addr, &len);
+
+ if (fd < 0 && errno != EINTR) {
+ TRACE("accept() failed");
+ return;
+ } else if (fd >= 0) {
+ TRACE("accepted connection");
+ break;
+ }
+ }
+
+ drv->channel_fd = fd;
+ vp_set_fd_handler(drv->channel_fd, vp_channel_read, NULL, drv);
+ /* dont accept anymore connections until channel_fd is closed */
+ vp_set_fd_handler(drv->listen_fd, NULL, NULL, NULL);
+}
--
1.7.0.4
next prev parent reply other threads:[~2010-10-22 18:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 18:43 [Qemu-devel] [RFC][PATCH 00/15] virtproxy: host/guest communication layer Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 01/15] virtproxy: base data structures and constants Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 02/15] virtproxy: qemu-vp, standalone daemon skeleton Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 03/15] virtproxy: add debug functions for virtproxy core Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 04/15] virtproxy: list look-up functions conns/oforwards/iforwards Michael Roth
2010-10-22 18:43 ` Michael Roth [this message]
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 06/15] virtproxy: add read handler for communication channel Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 07/15] virtproxy: add vp_new() VPDriver constructor Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 08/15] virtproxy: interfaces to set/remove/handle VPOForwards Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 09/15] virtproxy: add handler for data packets Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 10/15] virtproxy: add handler for control packet Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 11/15] virtproxy: add vp_handle_packet() Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 12/15] virtproxy: interfaces to set/remove VPIForwards Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 13/15] virtproxy: add read handler for proxied connections Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 14/15] virtproxy: Makefile/configure changes to build qemu-vp Michael Roth
2010-10-22 18:43 ` [Qemu-devel] [RFC][PATCH 15/15] virtproxy: qemu-vp, main logic Michael Roth
2010-10-23 11:26 ` [Qemu-devel] [RFC][PATCH 00/15] virtproxy: host/guest communication layer Blue Swirl
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=1287773011-24726-6-git-send-email-mdroth@linux.vnet.ibm.com \
--to=mdroth@linux.vnet.ibm.com \
--cc=abeekhof@redhat.com \
--cc=agl@linux.vnet.ibm.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.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 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).