[S390] cio: Trigger verification on device/path not operational.

Browse source

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>

...

This commit is contained in:

Cornelia Huck 2008-04-17 07:46:00 +02:00 • committed by Heiko Carstens

parent 22806dc1a8

commit fe6173d9b3

2 changed files with 13 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

9

drivers/s390/cio/device_ops.c

View file

6

drivers/s390/cio/device_status.c

View file