From: "Michael S. Tsirkin" <mst@redhat.com>
To: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
Cc: borntraeger@de.ibm.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2 RFC 1/3] virtio: add notify() callback to virtio_driver
Date: Thu, 21 Nov 2013 17:18:34 +0200 [thread overview]
Message-ID: <20131121151834.GA12032@redhat.com> (raw)
In-Reply-To: <1385045133-2165-2-git-send-email-graalfs@linux.vnet.ibm.com>
On Thu, Nov 21, 2013 at 03:45:31PM +0100, Heinz Graalfs wrote:
> Add an optional notify() callback to virtio_driver. A backend
> driver can provide this callback to perform actions for a lost
> device.
>
> notify() event values are inherited from virtio_ccw's notify()
> callback. We might want to support even more of them lateron.
>
> notify() return values are defined in include/linux/notifier.h.
>
> Signed-off-by: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
> ---
> drivers/virtio/virtio.c | 9 +++++++++
> include/linux/virtio.h | 10 ++++++++++
> 2 files changed, 19 insertions(+)
>
> diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c
> index ee59b74..a7f4302 100644
> --- a/drivers/virtio/virtio.c
> +++ b/drivers/virtio/virtio.c
> @@ -3,6 +3,7 @@
> #include <linux/virtio_config.h>
> #include <linux/module.h>
> #include <linux/idr.h>
> +#include <linux/notifier.h>
>
> /* Unique numbering for virtio devices. */
> static DEFINE_IDA(virtio_index_ida);
> @@ -186,6 +187,14 @@ void unregister_virtio_driver(struct virtio_driver *driver)
> }
> EXPORT_SYMBOL_GPL(unregister_virtio_driver);
>
> +int notify_virtio_device(struct virtio_device *vdev, int event)
> +{
> + struct virtio_driver *drv = drv_to_virtio(vdev->dev.driver);
> +
> + return drv->notify ? drv->notify(vdev, event) : NOTIFY_DONE;
> +}
> +EXPORT_SYMBOL_GPL(notify_virtio_device);
> +
> int register_virtio_device(struct virtio_device *dev)
> {
> int err;
> diff --git a/include/linux/virtio.h b/include/linux/virtio.h
> index f15f6e7..da18e9a 100644
> --- a/include/linux/virtio.h
> +++ b/include/linux/virtio.h
> @@ -110,6 +110,15 @@ int register_virtio_device(struct virtio_device *dev);
> void unregister_virtio_device(struct virtio_device *dev);
>
> /**
> + * notify event values
> + * @VDEV_GONE: device gone
> + */
> +enum {
> + VDEV_GONE = 1,
> +};
OK after understanding what this does, I think a
better name would be
VIRTIO_DEV_SURPRIZE_REMOVAL
this is what happened here.
> +int notify_virtio_device(struct virtio_device *dev, int event);
> +
> +/**
> * virtio_driver - operations for a virtio I/O driver
> * @driver: underlying device driver (populate name and owner).
> * @id_table: the ids serviced by this driver.
> @@ -129,6 +138,7 @@ struct virtio_driver {
> void (*scan)(struct virtio_device *dev);
> void (*remove)(struct virtio_device *dev);
> void (*config_changed)(struct virtio_device *dev);
> + int (*notify)(struct virtio_device *dev, int event);
> #ifdef CONFIG_PM
> int (*freeze)(struct virtio_device *dev);
> int (*restore)(struct virtio_device *dev);
> --
> 1.8.3.1
next prev parent reply other threads:[~2013-11-21 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 14:45 [PATCH v2 RFC 0/3] virtio: add new notify() callback to virtio_driver Heinz Graalfs
2013-11-21 14:45 ` [PATCH v2 RFC 1/3] virtio: add " Heinz Graalfs
2013-11-21 15:18 ` Michael S. Tsirkin [this message]
2013-11-21 14:45 ` [PATCH v2 RFC 2/3] virtio_blk: add virtblk_notify() as virtio_driver's notify() callback Heinz Graalfs
2013-11-21 14:45 ` [PATCH v2 RFC 3/3] virtio_ccw: invoke virtio_driver's notify() on CIO_GONE notification Heinz Graalfs
2013-11-21 15:15 ` Michael S. Tsirkin
2013-11-21 17:12 ` Heinz Graalfs
2013-11-21 18:31 ` Michael S. Tsirkin
2013-11-27 10:32 ` Heinz Graalfs
2013-11-27 10:42 ` Michael S. Tsirkin
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=20131121151834.GA12032@redhat.com \
--to=mst@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=graalfs@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.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).