[S390] cio: Trigger verification on device/path not operational.
authorCornelia Huck <cornelia.huck@de.ibm.com>
Thu, 17 Apr 2008 05:46:00 +0000 (07:46 +0200)
committerHeiko Carstens <heiko.carstens@de.ibm.com>
Thu, 17 Apr 2008 05:46:57 +0000 (07:46 +0200)
commitfe6173d9b33dba18ec462051750fb1b9abcd796d
tree393cf3a058e880365b069915d6cb8bad96ec36aa
parent22806dc1a8ffd88a7c7bdd070879e6e323db496a
[S390] cio: Trigger verification on device/path not operational.

Currently, we don't do much on no path or no device situations during
normal user I/O, since we rely on reports regarding those events by
the machine. If we trigger a path verification to bring our device
state up-to-date, we (a) may recover from path failures earlier and
(b) better handle situations where the hardware/hypervisor doesn't
give us enough notifications.

Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
drivers/s390/cio/device_ops.c
drivers/s390/cio/device_status.c