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 v2 05/18] xen/pvcalls: connect to a frontend Date: Fri, 19 May 2017 16:22:46 -0700 [thread overview] Message-ID: <1495236179-27776-5-git-send-email-sstabellini@kernel.org> (raw) In-Reply-To: <1495236179-27776-1-git-send-email-sstabellini@kernel.org> Introduce a per-frontend data structure named pvcalls_back_priv. It contains pointers to the command ring, its event channel, a list of active sockets and a tree of passive sockets (passing sockets need to be looked up from the id on listen, accept and poll commands, while active sockets only on release). It also has an unbound workqueue to schedule the work of parsing and executing commands on the command ring. socket_lock protects the two lists. In pvcalls_back_global, keep a list of connected frontends. Signed-off-by: Stefano Stabellini <stefano@aporeto.com> CC: boris.ostrovsky@oracle.com CC: jgross@suse.com --- drivers/xen/pvcalls-back.c | 95 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 95 insertions(+) diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c index b4da138..a48b0d9 100644 --- a/drivers/xen/pvcalls-back.c +++ b/drivers/xen/pvcalls-back.c @@ -33,9 +33,104 @@ struct pvcalls_back_global { struct semaphore frontends_lock; } pvcalls_back_global; +/* + * Per-frontend data structure. It contains pointers to the command + * ring, its event channel, a list of active sockets and a tree of + * passive sockets. + */ +struct pvcalls_back_priv { + struct list_head list; + struct xenbus_device *dev; + struct xen_pvcalls_sring *sring; + struct xen_pvcalls_back_ring ring; + int irq; + struct list_head socket_mappings; + struct radix_tree_root socketpass_mappings; + struct semaphore socket_lock; + atomic_t work; + struct workqueue_struct *wq; + struct work_struct register_work; +}; + +static void pvcalls_back_work(struct work_struct *work) +{ +} + +static irqreturn_t pvcalls_back_event(int irq, void *dev_id) +{ + return IRQ_HANDLED; +} + static int backend_connect(struct xenbus_device *dev) { + int err, evtchn; + grant_ref_t ring_ref; + void *addr = NULL; + struct pvcalls_back_priv *priv = NULL; + + priv = kzalloc(sizeof(struct pvcalls_back_priv), GFP_KERNEL); + if (!priv) + return -ENOMEM; + + err = xenbus_scanf(XBT_NIL, dev->otherend, "port", "%u", + &evtchn); + if (err != 1) { + err = -EINVAL; + xenbus_dev_fatal(dev, err, "reading %s/event-channel", + dev->otherend); + goto error; + } + + err = xenbus_scanf(XBT_NIL, dev->otherend, "ring-ref", "%u", &ring_ref); + if (err != 1) { + err = -EINVAL; + xenbus_dev_fatal(dev, err, "reading %s/ring-ref", + dev->otherend); + goto error; + } + + err = bind_interdomain_evtchn_to_irqhandler(dev->otherend_id, evtchn, + pvcalls_back_event, 0, + "pvcalls-backend", dev); + if (err < 0) + goto error; + priv->irq = err; + + priv->wq = alloc_workqueue("pvcalls_back_wq", WQ_UNBOUND, 1); + if (!priv->wq) { + err = -ENOMEM; + goto error; + } + + err = xenbus_map_ring_valloc(dev, &ring_ref, 1, &addr); + if (err < 0) + goto error; + priv->sring = addr; + + BACK_RING_INIT(&priv->ring, priv->sring, XEN_PAGE_SIZE * 1); + priv->dev = dev; + + INIT_WORK(&priv->register_work, pvcalls_back_work); + INIT_LIST_HEAD(&priv->socket_mappings); + INIT_RADIX_TREE(&priv->socketpass_mappings, GFP_KERNEL); + sema_init(&priv->socket_lock, 1); + dev_set_drvdata(&dev->dev, priv); + + down(&pvcalls_back_global.frontends_lock); + list_add_tail(&priv->list, &pvcalls_back_global.frontends); + up(&pvcalls_back_global.frontends_lock); + queue_work(priv->wq, &priv->register_work); + return 0; + + error: + if (addr != NULL) + xenbus_unmap_ring_vfree(dev, addr); + if (priv->wq) + destroy_workqueue(priv->wq); + unbind_from_irqhandler(priv->irq, dev); + kfree(priv); + return err; } static int backend_disconnect(struct xenbus_device *dev) -- 1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Stefano Stabellini <sstabellini@kernel.org> To: xen-devel@lists.xen.org Cc: jgross@suse.com, Stefano Stabellini <stefano@aporeto.com>, boris.ostrovsky@oracle.com, sstabellini@kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 05/18] xen/pvcalls: connect to a frontend Date: Fri, 19 May 2017 16:22:46 -0700 [thread overview] Message-ID: <1495236179-27776-5-git-send-email-sstabellini@kernel.org> (raw) In-Reply-To: <1495236179-27776-1-git-send-email-sstabellini@kernel.org> Introduce a per-frontend data structure named pvcalls_back_priv. It contains pointers to the command ring, its event channel, a list of active sockets and a tree of passive sockets (passing sockets need to be looked up from the id on listen, accept and poll commands, while active sockets only on release). It also has an unbound workqueue to schedule the work of parsing and executing commands on the command ring. socket_lock protects the two lists. In pvcalls_back_global, keep a list of connected frontends. Signed-off-by: Stefano Stabellini <stefano@aporeto.com> CC: boris.ostrovsky@oracle.com CC: jgross@suse.com --- drivers/xen/pvcalls-back.c | 95 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 95 insertions(+) diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c index b4da138..a48b0d9 100644 --- a/drivers/xen/pvcalls-back.c +++ b/drivers/xen/pvcalls-back.c @@ -33,9 +33,104 @@ struct pvcalls_back_global { struct semaphore frontends_lock; } pvcalls_back_global; +/* + * Per-frontend data structure. It contains pointers to the command + * ring, its event channel, a list of active sockets and a tree of + * passive sockets. + */ +struct pvcalls_back_priv { + struct list_head list; + struct xenbus_device *dev; + struct xen_pvcalls_sring *sring; + struct xen_pvcalls_back_ring ring; + int irq; + struct list_head socket_mappings; + struct radix_tree_root socketpass_mappings; + struct semaphore socket_lock; + atomic_t work; + struct workqueue_struct *wq; + struct work_struct register_work; +}; + +static void pvcalls_back_work(struct work_struct *work) +{ +} + +static irqreturn_t pvcalls_back_event(int irq, void *dev_id) +{ + return IRQ_HANDLED; +} + static int backend_connect(struct xenbus_device *dev) { + int err, evtchn; + grant_ref_t ring_ref; + void *addr = NULL; + struct pvcalls_back_priv *priv = NULL; + + priv = kzalloc(sizeof(struct pvcalls_back_priv), GFP_KERNEL); + if (!priv) + return -ENOMEM; + + err = xenbus_scanf(XBT_NIL, dev->otherend, "port", "%u", + &evtchn); + if (err != 1) { + err = -EINVAL; + xenbus_dev_fatal(dev, err, "reading %s/event-channel", + dev->otherend); + goto error; + } + + err = xenbus_scanf(XBT_NIL, dev->otherend, "ring-ref", "%u", &ring_ref); + if (err != 1) { + err = -EINVAL; + xenbus_dev_fatal(dev, err, "reading %s/ring-ref", + dev->otherend); + goto error; + } + + err = bind_interdomain_evtchn_to_irqhandler(dev->otherend_id, evtchn, + pvcalls_back_event, 0, + "pvcalls-backend", dev); + if (err < 0) + goto error; + priv->irq = err; + + priv->wq = alloc_workqueue("pvcalls_back_wq", WQ_UNBOUND, 1); + if (!priv->wq) { + err = -ENOMEM; + goto error; + } + + err = xenbus_map_ring_valloc(dev, &ring_ref, 1, &addr); + if (err < 0) + goto error; + priv->sring = addr; + + BACK_RING_INIT(&priv->ring, priv->sring, XEN_PAGE_SIZE * 1); + priv->dev = dev; + + INIT_WORK(&priv->register_work, pvcalls_back_work); + INIT_LIST_HEAD(&priv->socket_mappings); + INIT_RADIX_TREE(&priv->socketpass_mappings, GFP_KERNEL); + sema_init(&priv->socket_lock, 1); + dev_set_drvdata(&dev->dev, priv); + + down(&pvcalls_back_global.frontends_lock); + list_add_tail(&priv->list, &pvcalls_back_global.frontends); + up(&pvcalls_back_global.frontends_lock); + queue_work(priv->wq, &priv->register_work); + return 0; + + error: + if (addr != NULL) + xenbus_unmap_ring_vfree(dev, addr); + if (priv->wq) + destroy_workqueue(priv->wq); + unbind_from_irqhandler(priv->irq, dev); + kfree(priv); + return err; } static int backend_disconnect(struct xenbus_device *dev) -- 1.9.1 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-19 23:26 UTC|newest] Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-05-19 23:17 [PATCH v2 00/18] introduce the Xen PV Calls backend Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 01/18] xen: introduce the pvcalls interface header Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini 2017-05-25 22:04 ` Boris Ostrovsky 2017-05-25 22:04 ` Boris Ostrovsky 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-25 22:12 ` Boris Ostrovsky 2017-05-25 22:12 ` Boris Ostrovsky 2017-05-19 23:22 ` [PATCH v2 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-26 0:12 ` Boris Ostrovsky 2017-05-26 0:12 ` Boris Ostrovsky 2017-06-01 20:54 ` Stefano Stabellini 2017-06-01 20:54 ` Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini [this message] 2017-05-19 23:22 ` [PATCH v2 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini 2017-05-26 15:23 ` Boris Ostrovsky 2017-05-26 15:23 ` Boris Ostrovsky 2017-06-01 21:06 ` Stefano Stabellini 2017-06-01 21:06 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-26 15:32 ` Boris Ostrovsky 2017-05-26 15:32 ` Boris Ostrovsky 2017-06-02 18:21 ` Stefano Stabellini 2017-06-02 18:21 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 07/18] xen/pvcalls: implement socket command Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-26 15:53 ` Boris Ostrovsky 2017-05-26 15:53 ` Boris Ostrovsky 2017-06-02 18:35 ` Stefano Stabellini 2017-06-02 18:35 ` Stefano Stabellini 2017-05-26 18:58 ` Boris Ostrovsky 2017-05-26 18:58 ` Boris Ostrovsky 2017-06-02 18:41 ` Stefano Stabellini 2017-06-02 18:41 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 08/18] xen/pvcalls: implement connect command Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 09/18] xen/pvcalls: implement bind command Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 10/18] xen/pvcalls: implement listen command Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 11/18] xen/pvcalls: implement accept command Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-26 18:18 ` Boris Ostrovsky 2017-05-26 18:18 ` Boris Ostrovsky 2017-06-02 19:19 ` Stefano Stabellini 2017-06-02 19:19 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 12/18] xen/pvcalls: implement poll command Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 13/18] xen/pvcalls: implement release command Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 16/18] xen/pvcalls: implement read Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 17/18] xen/pvcalls: implement write Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-19 23:22 ` [PATCH v2 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini 2017-05-19 23:22 ` Stefano Stabellini 2017-05-25 22:02 ` [PATCH v2 01/18] xen: introduce the pvcalls interface header Boris Ostrovsky 2017-06-01 20:54 ` Stefano Stabellini 2017-06-01 20:54 ` Stefano Stabellini 2017-05-25 22:02 ` 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=1495236179-27776-5-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: linkBe 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.