diff options
author | Heinz Graalfs <graalfs@linux.vnet.ibm.com> | 2013-10-29 03:08:50 +0400 |
---|---|---|
committer | Rusty Russell <rusty@rustcorp.com.au> | 2013-10-29 04:58:11 +0400 |
commit | 46f9c2b925ac12e5ad8b8b7c90c71dacc9d5db37 (patch) | |
tree | 39b9bd752cb3cb43a5e11d4f0fc35f425f1d02e2 /drivers/virtio/virtio_ring.c | |
parent | 630b54d33493d1f67e79b148b5e361c5bbd3f29d (diff) | |
download | linux-46f9c2b925ac12e5ad8b8b7c90c71dacc9d5db37.tar.xz |
virtio_ring: change host notification API
Currently a host kick error is silently ignored and not reflected in
the virtqueue of a particular virtio device.
Changing the notify API for guest->host notification seems to be one
prerequisite in order to be able to handle such errors in the context
where the kick is triggered.
This patch changes the notify API. The notify function must return a
bool return value. It returns false if the host notification failed.
Signed-off-by: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Diffstat (limited to 'drivers/virtio/virtio_ring.c')
-rw-r--r-- | drivers/virtio/virtio_ring.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index 6547d46171b3..97dd51619b55 100644 --- a/drivers/virtio/virtio_ring.c +++ b/drivers/virtio/virtio_ring.c @@ -81,7 +81,7 @@ struct vring_virtqueue u16 last_used_idx; /* How to notify other side. FIXME: commonalize hcalls! */ - void (*notify)(struct virtqueue *vq); + bool (*notify)(struct virtqueue *vq); #ifdef DEBUG /* They're supposed to lock for us. */ @@ -744,7 +744,7 @@ struct virtqueue *vring_new_virtqueue(unsigned int index, struct virtio_device *vdev, bool weak_barriers, void *pages, - void (*notify)(struct virtqueue *), + bool (*notify)(struct virtqueue *), void (*callback)(struct virtqueue *), const char *name) { |