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 v3 09/18] xen/pvcalls: implement bind command
Date: Fri, 2 Jun 2017 12:31:46 -0700 [thread overview]
Message-ID: <1496431915-20774-9-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <1496431915-20774-1-git-send-email-sstabellini@kernel.org>
Allocate a socket. Track the allocated passive sockets with a new data
structure named sockpass_mapping. It contains an unbound workqueue to
schedule delayed work for the accept and poll commands. It also has a
reqcopy field to be used to store a copy of a request for delayed work.
Reads/writes to it are protected by a lock (the "copy_lock" spinlock).
Initialize the workqueue in pvcalls_back_bind.
Implement the bind command with inet_bind.
The pass_sk_data_ready event handler will be added later.
Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
CC: boris.ostrovsky@oracle.com
CC: jgross@suse.com
---
drivers/xen/pvcalls-back.c | 87 +++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 86 insertions(+), 1 deletion(-)
diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
index 3eb84ef..4a0cfa3 100644
--- a/drivers/xen/pvcalls-back.c
+++ b/drivers/xen/pvcalls-back.c
@@ -81,6 +81,18 @@ struct sock_mapping {
struct pvcalls_ioworker ioworker;
};
+struct sockpass_mapping {
+ struct list_head list;
+ struct pvcalls_fedata *priv;
+ struct socket *sock;
+ uint64_t id;
+ struct xen_pvcalls_request reqcopy;
+ spinlock_t copy_lock;
+ struct workqueue_struct *wq;
+ struct work_struct register_work;
+ void (*saved_data_ready)(struct sock *sk);
+};
+
static irqreturn_t pvcalls_back_conn_event(int irq, void *sock_map);
static int pvcalls_back_release_active(struct xenbus_device *dev,
struct pvcalls_fedata *priv,
@@ -261,10 +273,83 @@ static int pvcalls_back_release(struct xenbus_device *dev,
return 0;
}
+static void __pvcalls_back_accept(struct work_struct *work)
+{
+}
+
+static void pvcalls_pass_sk_data_ready(struct sock *sock)
+{
+}
+
static int pvcalls_back_bind(struct xenbus_device *dev,
struct xen_pvcalls_request *req)
{
- return 0;
+ struct pvcalls_fedata *priv;
+ int ret, err;
+ struct socket *sock;
+ struct sockpass_mapping *map = NULL;
+ struct xen_pvcalls_response *rsp;
+
+ priv = dev_get_drvdata(&dev->dev);
+
+ map = kzalloc(sizeof(*map), GFP_KERNEL);
+ if (map == NULL) {
+ ret = -ENOMEM;
+ goto out;
+ }
+
+ INIT_WORK(&map->register_work, __pvcalls_back_accept);
+ spin_lock_init(&map->copy_lock);
+ map->wq = alloc_workqueue("pvcalls_wq", WQ_UNBOUND, 1);
+ if (!map->wq) {
+ ret = -ENOMEM;
+ kfree(map);
+ goto out;
+ }
+
+ ret = sock_create(AF_INET, SOCK_STREAM, 0, &sock);
+ if (ret < 0) {
+ destroy_workqueue(map->wq);
+ kfree(map);
+ goto out;
+ }
+
+ ret = inet_bind(sock, (struct sockaddr *)&req->u.bind.addr,
+ req->u.bind.len);
+ if (ret < 0) {
+ destroy_workqueue(map->wq);
+ kfree(map);
+ goto out;
+ }
+
+ map->priv = priv;
+ map->sock = sock;
+ map->id = req->u.bind.id;
+
+ down(&priv->socket_lock);
+ err = radix_tree_insert(&priv->socketpass_mappings, map->id,
+ map);
+ up(&priv->socket_lock);
+ if (err) {
+ ret = err;
+ destroy_workqueue(map->wq);
+ kfree(map);
+ goto out;
+ }
+
+ write_lock_bh(&sock->sk->sk_callback_lock);
+ map->saved_data_ready = sock->sk->sk_data_ready;
+ sock->sk->sk_user_data = map;
+ sock->sk->sk_data_ready = pvcalls_pass_sk_data_ready;
+ write_unlock_bh(&sock->sk->sk_callback_lock);
+
+out:
+ rsp = RING_GET_RESPONSE(&priv->ring, priv->ring.rsp_prod_pvt++);
+ rsp->req_id = req->req_id;
+ rsp->cmd = req->cmd;
+ rsp->u.bind.id = req->u.bind.id;
+ rsp->ret = ret;
+ return ret;
}
static int pvcalls_back_listen(struct xenbus_device *dev,
--
1.9.1
next prev parent reply other threads:[~2017-06-02 19:34 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 19:31 [PATCH v3 00/18] introduce the Xen PV Calls backend Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-06-12 21:19 ` Boris Ostrovsky
2017-06-02 19:31 ` [PATCH v3 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-06-12 21:27 ` Boris Ostrovsky
2017-06-02 19:31 ` [PATCH v3 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini
2017-06-12 22:03 ` Boris Ostrovsky
2017-06-14 21:03 ` Stefano Stabellini
2017-06-15 14:33 ` Boris Ostrovsky
2017-06-15 18:54 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-06-13 6:06 ` Juergen Gross
2017-06-14 0:46 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-06-13 6:17 ` Juergen Gross
2017-06-14 0:46 ` Stefano Stabellini
2017-06-02 19:31 ` Stefano Stabellini [this message]
2017-06-13 7:00 ` [PATCH v3 09/18] xen/pvcalls: implement bind command Juergen Gross
2017-06-14 0:46 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-06-13 7:00 ` Juergen Gross
2017-06-02 19:31 ` [PATCH v3 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-06-13 7:24 ` Juergen Gross
2017-06-14 0:47 ` Stefano Stabellini
2017-06-14 6:32 ` Juergen Gross
2017-06-14 19:27 ` Stefano Stabellini
2017-06-15 6:58 ` Juergen Gross
2017-06-15 17:54 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-06-13 7:28 ` Juergen Gross
2017-06-14 0:47 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-06-13 7:39 ` Juergen Gross
2017-06-14 0:47 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-06-13 7:49 ` Juergen Gross
2017-06-14 0:54 ` Stefano Stabellini
2017-06-14 13:51 ` Boris Ostrovsky
2017-06-14 19:15 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini
2017-06-13 7:51 ` Juergen Gross
2017-06-14 0:56 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-06-13 7:56 ` Juergen Gross
2017-06-14 0:57 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-06-13 7:59 ` Juergen Gross
2017-06-14 1:00 ` Stefano Stabellini
2017-06-02 19:31 ` [PATCH v3 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini
2017-06-13 6:02 ` Juergen Gross
2017-06-13 23:46 ` Stefano Stabellini
2017-06-12 21:17 ` [PATCH v3 01/18] xen: introduce the pvcalls interface header Boris Ostrovsky
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=1496431915-20774-9-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).