s390x/ccw: make sure all ccw devices are properly reset
commit838fb84f83c84f00d15b1bede5e080b495644458
authorCornelia Huck <cohuck@redhat.com>
Mon, 7 May 2018 13:27:57 +0000 (7 15:27 +0200)
committerCornelia Huck <cohuck@redhat.com>
Mon, 14 May 2018 15:10:02 +0000 (14 17:10 +0200)
tree5b46969cc9e0ee5fa7d2f2932dcec9fdeacc2ea8
parent0c53057adb04d254bc09511880670c92ab185fc6
s390x/ccw: make sure all ccw devices are properly reset

Thomas reported that the subchannel for a  3270 device that ended up
in a broken state (status pending even though not enabled) did not
get out of that state even after a reboot (which involves a subsytem
reset). The reason for this is that the 3270 device did not define
a reset handler.

Let's fix this by introducing a base reset handler (set up for all
ccw devices) that resets the subchannel and have virtio-ccw call
its virtio-specific reset procedure in addition to that.

CC: qemu-stable@nongnu.org
Reported-by: Thomas Huth <thuth@redhat.com>
Suggested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Tested-by: Thomas Huth <thuth@redhat.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
hw/s390x/ccw-device.c
hw/s390x/virtio-ccw.c
hw/s390x/virtio-ccw.h