xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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 v7 06/18] xen/pvcalls: handle commands from the frontend
Date: Wed,  5 Jul 2017 14:50:46 -0700	[thread overview]
Message-ID: <1499291458-30231-6-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <1499291458-30231-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 | 125 +++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 125 insertions(+)

diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
index eb15d83..f55df4d 100644
--- a/drivers/xen/pvcalls-back.c
+++ b/drivers/xen/pvcalls-back.c
@@ -49,8 +49,133 @@ struct pvcalls_fedata {
 	struct semaphore socket_lock;
 };
 
+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:
+	{
+		struct pvcalls_fedata *fedata;
+		struct xen_pvcalls_response *rsp;
+
+		fedata = dev_get_drvdata(&dev->dev);
+		rsp = RING_GET_RESPONSE(
+				&fedata->ring, fedata->ring.rsp_prod_pvt++);
+		rsp->req_id = req->req_id;
+		rsp->cmd = req->cmd;
+		rsp->ret = -ENOTSUPP;
+		break;
+	}
+	}
+	return ret;
+}
+
+static void pvcalls_back_work(struct pvcalls_fedata *fedata)
+{
+	int notify, notify_all = 0, more = 1;
+	struct xen_pvcalls_request req;
+	struct xenbus_device *dev = fedata->dev;
+
+	while (more) {
+		while (RING_HAS_UNCONSUMED_REQUESTS(&fedata->ring)) {
+			RING_COPY_REQUEST(&fedata->ring,
+					  fedata->ring.req_cons++,
+					  &req);
+
+			if (!pvcalls_back_handle_cmd(dev, &req)) {
+				RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(
+					&fedata->ring, notify);
+				notify_all += notify;
+			}
+		}
+
+		if (notify_all) {
+			notify_remote_via_irq(fedata->irq);
+			notify_all = 0;
+		}
+
+		RING_FINAL_CHECK_FOR_REQUESTS(&fedata->ring, more);
+	}
+}
+ 
 static irqreturn_t pvcalls_back_event(int irq, void *dev_id)
 {
+	struct xenbus_device *dev = dev_id;
+	struct pvcalls_fedata *fedata = NULL;
+
+	if (dev == NULL)
+		return IRQ_HANDLED;
+
+	fedata = dev_get_drvdata(&dev->dev);
+	if (fedata == NULL)
+		return IRQ_HANDLED;
+
+	pvcalls_back_work(fedata);
 	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-07-05 21:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.10.1707051447010.2919@sstabellini-ThinkPad-X260>
2017-07-05 21:50 ` [PATCH v7 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-07-06  7:19     ` Juergen Gross
2017-07-05 21:50   ` [PATCH v7 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-07-06  7:20     ` Juergen Gross
2017-07-05 21:50   ` Stefano Stabellini [this message]
2017-07-06  7:23     ` [PATCH v7 06/18] xen/pvcalls: handle commands from the frontend Juergen Gross
2017-07-05 21:50   ` [PATCH v7 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 09/18] xen/pvcalls: implement bind command Stefano Stabellini
2017-07-06  7:25     ` Juergen Gross
2017-07-05 21:50   ` [PATCH v7 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-07-06  7:26     ` Juergen Gross
2017-07-05 21:50   ` [PATCH v7 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini
2017-07-06  7:27     ` Juergen Gross
2017-07-05 21:50   ` [PATCH v7 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-07-05 21:50   ` [PATCH v7 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini
     [not found]   ` <1499291458-30231-8-git-send-email-sstabellini@kernel.org>
2017-07-06  7:24     ` [PATCH v7 08/18] xen/pvcalls: implement connect command Juergen Gross

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=1499291458-30231-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 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).