Michael S. Tsirkin 6fbc198cf6 virtio_pci: fix virtio spec compliance on restore ... On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK This behaviour will break with hypervisors that assume spec compliant behaviour. It seems like a good idea to have this patch applied to stable branches to reduce the support butden for the hypervisors. Cc: stable@vger.kernel.org Cc: Amit Shah <amit.shah@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>		2014-10-15 10:24:53 +10:30
..
config.c	Remove all #inclusions of asm/system.h	2012-03-28 18:30:03 +01:00
Kconfig	drivers/virtio: remove depends on CONFIG_EXPERIMENTAL	2013-01-11 11:39:04 -08:00
Makefile	virtio: remove CONFIG_VIRTIO_RING	2012-09-28 15:05:15 +09:30
virtio_balloon.c	virtio_balloon: don't crash if virtqueue is broken.	2014-03-13 11:27:56 +10:30
virtio_mmio.c	virtio: mmio: fix signature checking for BE guests	2013-11-07 12:13:04 +10:30
virtio_pci.c	virtio_pci: fix virtio spec compliance on restore	2014-10-15 10:24:53 +10:30
virtio_ring.c	virtio: virtio_break_device() to mark all virtqueues broken.	2014-04-28 11:34:13 +09:30
virtio.c	virtio: convert bus code to use dev_groups	2013-10-16 18:40:57 -07:00