From: Juergen Gross <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: linux-kernel@vger.kernel.org, boris.ostrovsky@oracle.com,
Stefano Stabellini <stefano@aporeto.com>
Subject: Re: [PATCH v6 04/18] xen/pvcalls: xenbus state handling
Date: Tue, 4 Jul 2017 10:03:07 +0200 [thread overview]
Message-ID: <2dd8d8e1-4fc4-3d9e-0b74-b1704ac5e658@suse.com> (raw)
In-Reply-To: <1499116119-15638-4-git-send-email-sstabellini@kernel.org>
On 03/07/17 23:08, Stefano Stabellini wrote:
> Introduce the code to handle xenbus state changes.
>
> Implement the probe function for the pvcalls backend. Write the
> supported versions, max-page-order and function-calls nodes to xenstore,
> as required by the protocol.
>
> Introduce stub functions for disconnecting/connecting to a frontend.
>
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> CC: boris.ostrovsky@oracle.com
> CC: jgross@suse.com
> ---
> drivers/xen/pvcalls-back.c | 152 +++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 152 insertions(+)
>
> diff --git a/drivers/xen/pvcalls-back.c b/drivers/xen/pvcalls-back.c
> index 9044cf2..7bce750 100644
> --- a/drivers/xen/pvcalls-back.c
> +++ b/drivers/xen/pvcalls-back.c
> @@ -25,20 +25,172 @@
> #include <xen/xenbus.h>
> #include <xen/interface/io/pvcalls.h>
>
> +#define PVCALLS_VERSIONS "1"
> +#define MAX_RING_ORDER XENBUS_MAX_RING_GRANT_ORDER
> +
> struct pvcalls_back_global {
> struct list_head frontends;
> struct semaphore frontends_lock;
> } pvcalls_back_global;
>
> +static int backend_connect(struct xenbus_device *dev)
> +{
> + return 0;
> +}
> +
> +static int backend_disconnect(struct xenbus_device *dev)
> +{
> + return 0;
> +}
> +
> static int pvcalls_back_probe(struct xenbus_device *dev,
> const struct xenbus_device_id *id)
> {
> + int err, abort;
> + struct xenbus_transaction xbt;
> +
> +again:
> + abort = 1;
> +
> + err = xenbus_transaction_start(&xbt);
> + if (err) {
> + pr_warn("%s cannot create xenstore transaction\n", __func__);
> + return err;
> + }
> +
> + err = xenbus_printf(xbt, dev->nodename, "versions", "%s",
> + PVCALLS_VERSIONS);
> + if (err) {
> + pr_warn("%s write out 'version' failed\n", __func__);
s/version/versions/ ?
> + goto abort;
> + }
> +
> + err = xenbus_printf(xbt, dev->nodename, "max-page-order", "%u",
> + MAX_RING_ORDER);
> + if (err) {
> + pr_warn("%s write out 'max-page-order' failed\n", __func__);
> + goto abort;
> + }
> +
> + err = xenbus_printf(xbt, dev->nodename, "function-calls",
> + XENBUS_FUNCTIONS_CALLS);
> + if (err) {
> + pr_warn("%s write out 'function-calls' failed\n", __func__);
> + goto abort;
> + }
> +
> + abort = 0;
> +abort:
> + err = xenbus_transaction_end(xbt, abort);
> + if (err) {
> + if (err == -EAGAIN && !abort)
Hmm, while I don't think xenbus_transaction_end() will ever
return -EAGAIN in the abort case I'm not sure you should limit
the retry loop to the non-abort case.
> + goto again;
> + pr_warn("%s cannot complete xenstore transaction\n", __func__);
> + return err;
> + }
> +
> + xenbus_switch_state(dev, XenbusStateInitWait);
I don't think you should switch state in case of abort set, no?
Juergen
next prev parent reply other threads:[~2017-07-04 8:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 21:08 [PATCH v6 00/18] introduce the Xen PV Calls backend Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 01/18] xen: introduce the pvcalls interface header Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 02/18] xen/pvcalls: introduce the pvcalls xenbus backend Stefano Stabellini
2017-07-04 8:04 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 03/18] xen/pvcalls: initialize the module and register the " Stefano Stabellini
2017-07-04 8:04 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 04/18] xen/pvcalls: xenbus state handling Stefano Stabellini
2017-07-04 8:03 ` Juergen Gross [this message]
2017-07-05 20:24 ` Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 05/18] xen/pvcalls: connect to a frontend Stefano Stabellini
2017-07-04 6:59 ` Juergen Gross
2017-07-05 20:29 ` Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 06/18] xen/pvcalls: handle commands from the frontend Stefano Stabellini
2017-07-04 6:57 ` Juergen Gross
2017-07-05 20:43 ` Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 07/18] xen/pvcalls: implement socket command Stefano Stabellini
2017-07-04 7:52 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 08/18] xen/pvcalls: implement connect command Stefano Stabellini
2017-07-04 7:14 ` Juergen Gross
2017-07-05 21:09 ` Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 09/18] xen/pvcalls: implement bind command Stefano Stabellini
2017-07-04 7:24 ` Juergen Gross
2017-07-05 21:18 ` Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 10/18] xen/pvcalls: implement listen command Stefano Stabellini
2017-07-04 7:51 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 11/18] xen/pvcalls: implement accept command Stefano Stabellini
2017-07-04 7:26 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 12/18] xen/pvcalls: implement poll command Stefano Stabellini
2017-07-04 7:28 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 13/18] xen/pvcalls: implement release command Stefano Stabellini
2017-07-04 7:30 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 14/18] xen/pvcalls: disconnect and module_exit Stefano Stabellini
2017-07-04 7:32 ` Juergen Gross
2017-07-05 21:22 ` Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 15/18] xen/pvcalls: implement the ioworker functions Stefano Stabellini
2017-07-04 7:48 ` Juergen Gross
2017-07-05 21:26 ` Stefano Stabellini
2017-07-03 21:08 ` [PATCH v6 16/18] xen/pvcalls: implement read Stefano Stabellini
2017-07-04 7:36 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 17/18] xen/pvcalls: implement write Stefano Stabellini
2017-07-04 7:49 ` Juergen Gross
2017-07-03 21:08 ` [PATCH v6 18/18] xen: introduce a Kconfig option to enable the pvcalls backend Stefano Stabellini
2017-07-04 7:50 ` Juergen Gross
2017-07-04 8:05 ` [PATCH v6 01/18] xen: introduce the pvcalls interface header 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=2dd8d8e1-4fc4-3d9e-0b74-b1704ac5e658@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@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
all inboxes | Powered by JetHome®