All of lore.kernel.org
 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 v2 06/18] xen/pvcalls: handle commands from the frontend
Date: Fri, 19 May 2017 16:22:47 -0700	[thread overview]
Message-ID: <1495236179-27776-6-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <1495236179-27776-1-git-send-email-sstabellini@kernel.org>

When the other end notifies us that there are commands to be read
(pvcalls_back_event), wake up the backend thread to parse the command.

The command ring works like most other Xen rings, so use the usual
ring macros to read and write to it. The functions implementing the
commands are empty stubs for now.

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

diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
index a48b0d9..9dc8a28 100644
--- a/drivers/xen/pvcalls-back.c
+++ b/drivers/xen/pvcalls-back.c
@@ -52,12 +52,127 @@ struct pvcalls_back_priv {
 	struct work_struct register_work;
 };
 
+static int pvcalls_back_socket(struct xenbus_device *dev,
+		struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_connect(struct xenbus_device *dev,
+				struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_release(struct xenbus_device *dev,
+				struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_bind(struct xenbus_device *dev,
+			     struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_listen(struct xenbus_device *dev,
+			       struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_accept(struct xenbus_device *dev,
+			       struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_poll(struct xenbus_device *dev,
+			     struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_handle_cmd(struct xenbus_device *dev,
+				   struct xen_pvcalls_request *req)
+{
+	int ret = 0;
+
+	switch (req->cmd) {
+	case PVCALLS_SOCKET:
+		ret = pvcalls_back_socket(dev, req);
+		break;
+	case PVCALLS_CONNECT:
+		ret = pvcalls_back_connect(dev, req);
+		break;
+	case PVCALLS_RELEASE:
+		ret = pvcalls_back_release(dev, req);
+		break;
+	case PVCALLS_BIND:
+		ret = pvcalls_back_bind(dev, req);
+		break;
+	case PVCALLS_LISTEN:
+		ret = pvcalls_back_listen(dev, req);
+		break;
+	case PVCALLS_ACCEPT:
+		ret = pvcalls_back_accept(dev, req);
+		break;
+	case PVCALLS_POLL:
+		ret = pvcalls_back_poll(dev, req);
+		break;
+	default:
+		ret = -ENOTSUPP;
+		break;
+	}
+	return ret;
+}
+
 static void pvcalls_back_work(struct work_struct *work)
 {
+	struct pvcalls_back_priv *priv = container_of(work,
+		struct pvcalls_back_priv, register_work);
+	int notify, notify_all = 0, more = 1;
+	struct xen_pvcalls_request req;
+	struct xenbus_device *dev = priv->dev;
+
+	atomic_set(&priv->work, 1);
+
+	while (more || !atomic_dec_and_test(&priv->work)) {
+		while (RING_HAS_UNCONSUMED_REQUESTS(&priv->ring)) {
+			RING_COPY_REQUEST(&priv->ring,
+					  priv->ring.req_cons++,
+					  &req);
+
+			if (!pvcalls_back_handle_cmd(dev, &req)) {
+				RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(
+					&priv->ring, notify);
+				notify_all += notify;
+			}
+		}
+
+		if (notify_all)
+			notify_remote_via_irq(priv->irq);
+
+		RING_FINAL_CHECK_FOR_REQUESTS(&priv->ring, more);
+	}
 }
 
 static irqreturn_t pvcalls_back_event(int irq, void *dev_id)
 {
+	struct xenbus_device *dev = dev_id;
+	struct pvcalls_back_priv *priv = NULL;
+
+	if (dev == NULL)
+		return IRQ_HANDLED;
+
+	priv = dev_get_drvdata(&dev->dev);
+	if (priv == NULL)
+		return IRQ_HANDLED;
+
+	atomic_inc(&priv->work);
+	queue_work(priv->wq, &priv->register_work);
+
 	return IRQ_HANDLED;
 }
 
-- 
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 06/18] xen/pvcalls: handle commands from the frontend
Date: Fri, 19 May 2017 16:22:47 -0700	[thread overview]
Message-ID: <1495236179-27776-6-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <1495236179-27776-1-git-send-email-sstabellini@kernel.org>

When the other end notifies us that there are commands to be read
(pvcalls_back_event), wake up the backend thread to parse the command.

The command ring works like most other Xen rings, so use the usual
ring macros to read and write to it. The functions implementing the
commands are empty stubs for now.

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

diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
index a48b0d9..9dc8a28 100644
--- a/drivers/xen/pvcalls-back.c
+++ b/drivers/xen/pvcalls-back.c
@@ -52,12 +52,127 @@ struct pvcalls_back_priv {
 	struct work_struct register_work;
 };
 
+static int pvcalls_back_socket(struct xenbus_device *dev,
+		struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_connect(struct xenbus_device *dev,
+				struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_release(struct xenbus_device *dev,
+				struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_bind(struct xenbus_device *dev,
+			     struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_listen(struct xenbus_device *dev,
+			       struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_accept(struct xenbus_device *dev,
+			       struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_poll(struct xenbus_device *dev,
+			     struct xen_pvcalls_request *req)
+{
+	return 0;
+}
+
+static int pvcalls_back_handle_cmd(struct xenbus_device *dev,
+				   struct xen_pvcalls_request *req)
+{
+	int ret = 0;
+
+	switch (req->cmd) {
+	case PVCALLS_SOCKET:
+		ret = pvcalls_back_socket(dev, req);
+		break;
+	case PVCALLS_CONNECT:
+		ret = pvcalls_back_connect(dev, req);
+		break;
+	case PVCALLS_RELEASE:
+		ret = pvcalls_back_release(dev, req);
+		break;
+	case PVCALLS_BIND:
+		ret = pvcalls_back_bind(dev, req);
+		break;
+	case PVCALLS_LISTEN:
+		ret = pvcalls_back_listen(dev, req);
+		break;
+	case PVCALLS_ACCEPT:
+		ret = pvcalls_back_accept(dev, req);
+		break;
+	case PVCALLS_POLL:
+		ret = pvcalls_back_poll(dev, req);
+		break;
+	default:
+		ret = -ENOTSUPP;
+		break;
+	}
+	return ret;
+}
+
 static void pvcalls_back_work(struct work_struct *work)
 {
+	struct pvcalls_back_priv *priv = container_of(work,
+		struct pvcalls_back_priv, register_work);
+	int notify, notify_all = 0, more = 1;
+	struct xen_pvcalls_request req;
+	struct xenbus_device *dev = priv->dev;
+
+	atomic_set(&priv->work, 1);
+
+	while (more || !atomic_dec_and_test(&priv->work)) {
+		while (RING_HAS_UNCONSUMED_REQUESTS(&priv->ring)) {
+			RING_COPY_REQUEST(&priv->ring,
+					  priv->ring.req_cons++,
+					  &req);
+
+			if (!pvcalls_back_handle_cmd(dev, &req)) {
+				RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(
+					&priv->ring, notify);
+				notify_all += notify;
+			}
+		}
+
+		if (notify_all)
+			notify_remote_via_irq(priv->irq);
+
+		RING_FINAL_CHECK_FOR_REQUESTS(&priv->ring, more);
+	}
 }
 
 static irqreturn_t pvcalls_back_event(int irq, void *dev_id)
 {
+	struct xenbus_device *dev = dev_id;
+	struct pvcalls_back_priv *priv = NULL;
+
+	if (dev == NULL)
+		return IRQ_HANDLED;
+
+	priv = dev_get_drvdata(&dev->dev);
+	if (priv == NULL)
+		return IRQ_HANDLED;
+
+	atomic_inc(&priv->work);
+	queue_work(priv->wq, &priv->register_work);
+
 	return IRQ_HANDLED;
 }
 
-- 
1.9.1


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  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   ` [PATCH v2 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-05-19 23:22     ` 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   ` Stefano Stabellini [this message]
2017-05-19 23:22     ` [PATCH v2 06/18] xen/pvcalls: handle commands from the frontend 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-6-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 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.