linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: xen-devel@lists.xen.org
Cc: linux-kernel@vger.kernel.org, sstabellini@kernel.org,
	jgross@suse.com, boris.ostrovsky@oracle.com,
	Stefano Stabellini <stefano@aporeto.com>
Subject: [PATCH v5 10/18] xen/pvcalls: implement listen command
Date: Thu, 22 Jun 2017 12:14:19 -0700	[thread overview]
Message-ID: <1498158867-25426-10-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <1498158867-25426-1-git-send-email-sstabellini@kernel.org>

Call inet_listen to implement the listen command.

Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
CC: boris.ostrovsky@oracle.com
CC: jgross@suse.com
---
 drivers/xen/pvcalls-back.c | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
index 2c0bfef..2a47425 100644
--- a/drivers/xen/pvcalls-back.c
+++ b/drivers/xen/pvcalls-back.c
@@ -361,6 +361,27 @@ static int pvcalls_back_bind(struct xenbus_device *dev,
 static int pvcalls_back_listen(struct xenbus_device *dev,
 			       struct xen_pvcalls_request *req)
 {
+	struct pvcalls_fedata *fedata;
+	int ret = -EINVAL;
+	struct sockpass_mapping *map;
+	struct xen_pvcalls_response *rsp;
+
+	fedata = dev_get_drvdata(&dev->dev);
+
+	down(&fedata->socket_lock);
+	map = radix_tree_lookup(&fedata->socketpass_mappings, req->u.listen.id);
+	up(&fedata->socket_lock);
+	if (map == NULL)
+		goto out;
+
+	ret = inet_listen(map->sock, req->u.listen.backlog);
+
+out:
+	rsp = RING_GET_RESPONSE(&fedata->ring, fedata->ring.rsp_prod_pvt++);
+	rsp->req_id = req->req_id;
+	rsp->cmd = req->cmd;
+	rsp->u.listen.id = req->u.listen.id;
+	rsp->ret = ret;
 	return 0;
 }
 
-- 
1.9.1

  parent reply	other threads:[~2017-06-22 19:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 19:14 [PATCH v5 00/18] introduce the Xen PV Calls backend Stefano Stabellini
2017-06-22 19:14 ` [PATCH v5 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini
2017-07-03 11:23     ` Juergen Gross
2017-07-03 20:57       ` Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 09/18] xen/pvcalls: implement bind command Stefano Stabellini
2017-06-22 19:14   ` Stefano Stabellini [this message]
2017-06-22 19:14   ` [PATCH v5 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-06-22 19:14   ` [PATCH v5 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini

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=1498158867-25426-10-git-send-email-sstabellini@kernel.org \
    --to=sstabellini@kernel.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefano@aporeto.com \
    --cc=xen-devel@lists.xen.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).