| commit | fa8b0ca5d1b69975b715a259d3586cadf7a5280f | |
| author | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Tue, 23 Jun 2015 13:46:31 +0000 (23 15:46 +0200) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Tue, 30 Jun 2015 07:34:57 +0000 (30 09:34 +0200) | ||
| tree | cceb712e11b2c158f334cadf2d12cdf2f0e5053b | treesnapshot (tar.gz zip) |
| parent | d2966f804d70a244f5dde395fc5d22a50ed3e74e | commitdiff |
virtio-ccw: complete handling of guest-initiated resets
For a guest-initiated reset, we need to not only reset the virtio device,
but also reset the VirtioCcwDevice into a clean state. This includes
resetting the indicators, or else a guest will not be able to e.g.
switch from classic interrupts to adapter interrupts.
Split off this routine into a new function virtio_ccw_reset_virtio()
to make the distinction between resetting the virtio-related devices
and the base subchannel device clear.
CC: qemu-stable@nongnu.org
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
For a guest-initiated reset, we need to not only reset the virtio device,
but also reset the VirtioCcwDevice into a clean state. This includes
resetting the indicators, or else a guest will not be able to e.g.
switch from classic interrupts to adapter interrupts.
Split off this routine into a new function virtio_ccw_reset_virtio()
to make the distinction between resetting the virtio-related devices
and the base subchannel device clear.
CC: qemu-stable@nongnu.org
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
| hw/s390x/virtio-ccw.c | diffblobblamehistory |