mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v1 01/13] xen/pvcalls: introduce the pvcalls xenbus frontend
Date: Mon, 24 Jul 2017 21:06:20 +0200	[thread overview]
Message-ID: <7905bebe-39a0-380f-139d-66ee48c7e853@suse.com> (raw)
In-Reply-To: <1500682323-25940-1-git-send-email-sstabellini@kernel.org>

On 22/07/17 02:11, Stefano Stabellini wrote:
> Introduce a xenbus frontend for the pvcalls protocol, as defined by
> https://xenbits.xen.org/docs/unstable/misc/pvcalls.html.
> 
> This patch only adds the stubs, the code will be added by the following
> patches.
> 
> Signed-off-by: Stefano Stabellini <stefano@aporeto.com>
> CC: boris.ostrovsky@oracle.com
> CC: jgross@suse.com
> ---
>  drivers/xen/pvcalls-front.c | 68 +++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 68 insertions(+)
>  create mode 100644 drivers/xen/pvcalls-front.c
> 
> diff --git a/drivers/xen/pvcalls-front.c b/drivers/xen/pvcalls-front.c
> new file mode 100644
> index 0000000..173e204
> --- /dev/null
> +++ b/drivers/xen/pvcalls-front.c
> @@ -0,0 +1,68 @@
> +/*
> + * (c) 2017 Stefano Stabellini <stefano@aporeto.com>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> + * GNU General Public License for more details.
> + */
> +
> +#include <linux/module.h>
> +
> +#include <xen/events.h>
> +#include <xen/grant_table.h>
> +#include <xen/xen.h>
> +#include <xen/xenbus.h>
> +#include <xen/interface/io/pvcalls.h>
> +
> +static const struct xenbus_device_id pvcalls_front_ids[] = {
> +	{ "pvcalls" },
> +	{ "" }
> +};
> +
> +static int pvcalls_front_remove(struct xenbus_device *dev)
> +{
> +	return 0;
> +}
> +
> +static int pvcalls_front_probe(struct xenbus_device *dev,
> +			  const struct xenbus_device_id *id)
> +{
> +	return 0;
> +}
> +
> +static int pvcalls_front_resume(struct xenbus_device *dev)
> +{
> +	dev_warn(&dev->dev, "suspsend/resume unsupported\n");
> +	return 0;
> +}

Why are you adding a resume function doing nothing but issuing a
message? Just omit it.


Juergen

> +
> +static void pvcalls_front_changed(struct xenbus_device *dev,
> +			    enum xenbus_state backend_state)
> +{
> +}
> +
> +static struct xenbus_driver pvcalls_front_driver = {
> +	.ids = pvcalls_front_ids,
> +	.probe = pvcalls_front_probe,
> +	.remove = pvcalls_front_remove,
> +	.resume = pvcalls_front_resume,
> +	.otherend_changed = pvcalls_front_changed,
> +};
> +
> +static int __init pvcalls_frontend_init(void)
> +{
> +	if (!xen_domain())
> +		return -ENODEV;
> +
> +	pr_info("Initialising Xen pvcalls frontend driver\n");
> +
> +	return xenbus_register_frontend(&pvcalls_front_driver);
> +}
> +
> +module_init(pvcalls_frontend_init);
> 

  parent reply	other threads:[~2017-07-24 19:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-22  0:11 [PATCH v1 00/13] introduce the Xen PV Calls frontend Stefano Stabellini
2017-07-22  0:11 ` [PATCH v1 01/13] xen/pvcalls: introduce the pvcalls xenbus frontend Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 02/13] xen/pvcalls: connect to the backend Stefano Stabellini
2017-07-24 19:23     ` Juergen Gross
2017-07-25 20:10       ` Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 03/13] xen/pvcalls: implement socket command and handle events Stefano Stabellini
2017-07-24 19:29     ` Juergen Gross
2017-07-25 20:43       ` Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 04/13] xen/pvcalls: implement connect command Stefano Stabellini
2017-07-24 19:40     ` Juergen Gross
2017-07-24 22:45       ` Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 05/13] xen/pvcalls: implement bind command Stefano Stabellini
2017-07-24 19:43     ` Juergen Gross
2017-07-24 22:51       ` Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 06/13] xen/pvcalls: implement listen command Stefano Stabellini
2017-07-24 19:44     ` Juergen Gross
2017-07-24 22:51       ` Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 07/13] xen/pvcalls: implement accept command Stefano Stabellini
2017-07-24 19:47     ` Juergen Gross
2017-07-24 22:53       ` Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 08/13] xen/pvcalls: implement sendmsg Stefano Stabellini
2017-07-24 19:51     ` Juergen Gross
2017-07-24 22:38       ` Stefano Stabellini
2017-07-22  0:11   ` [PATCH v1 09/13] xen/pvcalls: implement recvmsg Stefano Stabellini
2017-07-24 19:56     ` Juergen Gross
2017-07-24 22:37       ` Stefano Stabellini
2017-07-22  0:12   ` [PATCH v1 10/13] xen/pvcalls: implement poll command Stefano Stabellini
2017-07-24 20:08     ` Juergen Gross
2017-07-25 20:59       ` Stefano Stabellini
2017-07-22  0:12   ` [PATCH v1 11/13] xen/pvcalls: implement release command Stefano Stabellini
2017-07-24 20:14     ` Juergen Gross
2017-07-25 21:07       ` Stefano Stabellini
2017-07-22  0:12   ` [PATCH v1 12/13] xen/pvcalls: implement frontend disconnect Stefano Stabellini
2017-07-24 20:16     ` Juergen Gross
2017-07-22  0:12   ` [PATCH v1 13/13] xen: introduce a Kconfig option to enable the pvcalls frontend Stefano Stabellini
2017-07-24 20:17     ` Juergen Gross
2017-07-24 22:36       ` Stefano Stabellini
2017-07-24 19:06   ` Juergen Gross [this message]
2017-07-24 22:32     ` [PATCH v1 01/13] xen/pvcalls: introduce the pvcalls xenbus frontend Stefano Stabellini

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=7905bebe-39a0-380f-139d-66ee48c7e853@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®