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 12/18] xen/pvcalls: implement poll command
Date: Thu, 22 Jun 2017 12:14:21 -0700 [thread overview]
Message-ID: <1498158867-25426-12-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <1498158867-25426-1-git-send-email-sstabellini@kernel.org>
Implement poll on passive sockets by requesting a delayed response with
mappass->reqcopy, and reply back when there is data on the passive
socket.
Poll on active socket is unimplemented as by the spec, as the frontend
should just wait for events and check the indexes on the indexes page.
Only support one outstanding poll (or accept) request for every passive
socket at any given time.
Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
CC: boris.ostrovsky@oracle.com
CC: jgross@suse.com
---
drivers/xen/pvcalls-back.c | 73 +++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 72 insertions(+), 1 deletion(-)
diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
index 62738e4..5b2ef60 100644
--- a/drivers/xen/pvcalls-back.c
+++ b/drivers/xen/pvcalls-back.c
@@ -352,11 +352,33 @@ static void __pvcalls_back_accept(struct work_struct *work)
static void pvcalls_pass_sk_data_ready(struct sock *sock)
{
struct sockpass_mapping *mappass = sock->sk_user_data;
+ struct pvcalls_fedata *fedata;
+ struct xen_pvcalls_response *rsp;
+ unsigned long flags;
+ int notify;
if (mappass == NULL)
return;
- queue_work(mappass->wq, &mappass->register_work);
+ fedata = mappass->fedata;
+ spin_lock_irqsave(&mappass->copy_lock, flags);
+ if (mappass->reqcopy.cmd == PVCALLS_POLL) {
+ rsp = RING_GET_RESPONSE(&fedata->ring, fedata->ring.rsp_prod_pvt++);
+ rsp->req_id = mappass->reqcopy.req_id;
+ rsp->u.poll.id = mappass->reqcopy.u.poll.id;
+ rsp->cmd = mappass->reqcopy.cmd;
+ rsp->ret = 0;
+
+ mappass->reqcopy.cmd = 0;
+ spin_unlock_irqrestore(&mappass->copy_lock, flags);
+
+ RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&fedata->ring, notify);
+ if (notify)
+ notify_remote_via_irq(mappass->fedata->irq);
+ } else {
+ spin_unlock_irqrestore(&mappass->copy_lock, flags);
+ queue_work(mappass->wq, &mappass->register_work);
+ }
}
static int pvcalls_back_bind(struct xenbus_device *dev,
@@ -507,6 +529,55 @@ static int pvcalls_back_accept(struct xenbus_device *dev,
static int pvcalls_back_poll(struct xenbus_device *dev,
struct xen_pvcalls_request *req)
{
+ struct pvcalls_fedata *fedata;
+ struct sockpass_mapping *mappass;
+ struct xen_pvcalls_response *rsp;
+ struct inet_connection_sock *icsk;
+ struct request_sock_queue *queue;
+ unsigned long flags;
+ int ret;
+ bool data;
+
+ fedata = dev_get_drvdata(&dev->dev);
+
+ down(&fedata->socket_lock);
+ mappass = radix_tree_lookup(&fedata->socketpass_mappings, req->u.poll.id);
+ up(&fedata->socket_lock);
+ if (mappass == NULL)
+ return -EINVAL;
+
+ /*
+ * Limitation of the current implementation: only support one
+ * concurrent accept or poll call on one socket.
+ */
+ spin_lock_irqsave(&mappass->copy_lock, flags);
+ if (mappass->reqcopy.cmd != 0) {
+ ret = -EINTR;
+ goto out;
+ }
+
+ mappass->reqcopy = *req;
+ icsk = inet_csk(mappass->sock->sk);
+ queue = &icsk->icsk_accept_queue;
+ data = queue->rskq_accept_head != NULL;
+ if (data) {
+ mappass->reqcopy.cmd = 0;
+ ret = 0;
+ goto out;
+ }
+ spin_unlock_irqrestore(&mappass->copy_lock, flags);
+
+ /* Tell the caller we don't need to send back a notification yet */
+ return -1;
+
+out:
+ spin_unlock_irqrestore(&mappass->copy_lock, flags);
+
+ rsp = RING_GET_RESPONSE(&fedata->ring, fedata->ring.rsp_prod_pvt++);
+ rsp->req_id = req->req_id;
+ rsp->cmd = req->cmd;
+ rsp->u.poll.id = req->u.poll.id;
+ rsp->ret = ret;
return 0;
}
--
1.9.1
next prev parent reply other threads:[~2017-06-22 19:15 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 ` [PATCH v5 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-06-22 19:14 ` [PATCH v5 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-06-22 19:14 ` Stefano Stabellini [this message]
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-12-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).