Re: [PATCH RFC 0/3] virtio: add new notify() callback to virtio_driver

2013-11-21 Thread Michael S. Tsirkin
On Thu, Nov 21, 2013 at 03:43:51PM +0100, Heinz Graalfs wrote: On 21/11/13 07:47, Michael S. Tsirkin wrote: On Wed, Nov 20, 2013 at 04:22:00PM +0100, Heinz Graalfs wrote: Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are

Re: [PATCH RFC 0/3] virtio: add new notify() callback to virtio_driver

2013-11-21 Thread Heinz Graalfs
On 21/11/13 07:47, Michael S. Tsirkin wrote: On Wed, Nov 20, 2013 at 04:22:00PM +0100, Heinz Graalfs wrote: Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This

Re: [PATCH RFC 0/3] virtio: add new notify() callback to virtio_driver

2013-11-21 Thread Heinz Graalfs
On 21/11/13 15:58, Michael S. Tsirkin wrote: On Thu, Nov 21, 2013 at 03:43:51PM +0100, Heinz Graalfs wrote: On 21/11/13 07:47, Michael S. Tsirkin wrote: On Wed, Nov 20, 2013 at 04:22:00PM +0100, Heinz Graalfs wrote: Hi, when an active virtio block device is hot-unplugged from a KVM guest,

[PATCH RFC 0/3] virtio: add new notify() callback to virtio_driver

2013-11-20 Thread Heinz Graalfs
Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request queueing when a lost block device is detected, resulting in

Re: [PATCH RFC 0/3] virtio: add new notify() callback to virtio_driver

2013-11-20 Thread Michael S. Tsirkin
On Wed, Nov 20, 2013 at 04:22:00PM +0100, Heinz Graalfs wrote: Hi, when an active virtio block device is hot-unplugged from a KVM guest, running affected guest user applications are not aware of any errors that occur due to the lost device. This patch-set adds code to avoid further request