On Thu, 5 Jul 2018 13:25:43 -0400
"Jason J. Herne" <jjhe...@linux.ibm.com> wrote:
> If a vfio-ccw device is left in an error state (example: pending unit
> check) then it is possible for that state to persist for a vfio-ccw device
> even
> after the enable subchannel that we do to bring the device online. If this
> state
> is allowed to persist then even simple I/O operations will needlessly fail. A
> basic sense ccw is used to clear this error state for the boot device.
Another thing: What about unsolicited interrupts? I.e., you enable the
subchannel, and then it becomes pending with unsolicited status. Do you
have any handling for that (or plan to add it)?
We could ignore that for virtio devices, but probably not for dasds.
>
> Signed-off-by: Jason J. Herne <jjhe...@linux.ibm.com>
> ---
> pc-bios/s390-ccw/cio.c | 13 +++++++++++++
> pc-bios/s390-ccw/cio.h | 13 +++++++++++++
> pc-bios/s390-ccw/main.c | 5 +++++
> 3 files changed, 31 insertions(+)
> diff --git a/pc-bios/s390-ccw/main.c b/pc-bios/s390-ccw/main.c
> index 2bccfa7..e0ce59b 100644
> --- a/pc-bios/s390-ccw/main.c
> +++ b/pc-bios/s390-ccw/main.c
> @@ -201,12 +201,17 @@ static void virtio_setup(void)
>
> int main(void)
> {
> + SenseData sd;
> +
> sclp_setup();
> cio_setup();
> boot_setup();
> find_boot_device();
> enable_subchannel(blk_schid);
>
> + /* Clear any outstanding device error conditions */
> + basic_sense(blk_schid, &sd);
Hmm. Could an error condition reassert itself after it was cleared?
Probably not worth spending too much time on, though.
> +
> switch (cu_type(blk_schid)) {
> case 0x3990: /* Real DASD device */
> dasd_ipl(blk_schid); /* no return */
