On Fri, 24 Jan 2020 11:08:12 -0500
Eric Farman <farman@xxxxxxxxxxxxx> wrote:
> On 1/24/20 10:33 AM, Cornelia Huck wrote:
> > On Fri, 24 Jan 2020 15:54:55 +0100
> > Eric Farman <farman@xxxxxxxxxxxxx> wrote:
> >> diff --git a/drivers/s390/cio/vfio_ccw_drv.c b/drivers/s390/cio/vfio_ccw_drv.c
> >> index e401a3d0aa57..a8ab256a217b 100644
> >> --- a/drivers/s390/cio/vfio_ccw_drv.c
> >> +++ b/drivers/s390/cio/vfio_ccw_drv.c
> >> @@ -90,8 +90,8 @@ static void vfio_ccw_sch_io_todo(struct work_struct *work)
> >> is_final = !(scsw_actl(&irb->scsw) &
> >> (SCSW_ACTL_DEVACT | SCSW_ACTL_SCHACT));
> >> if (scsw_is_solicited(&irb->scsw)) {
> >> - cp_update_scsw(&private->cp, &irb->scsw);
> >> - if (is_final && private->state == VFIO_CCW_STATE_CP_PENDING)
> >> + if (cp_update_scsw(&private->cp, &irb->scsw) &&
> >> + is_final && private->state == VFIO_CCW_STATE_CP_PENDING)
> >
> > ...but I still wonder why is_final is not catching non-ssch related
> > interrupts, as I thought it would. We might want to adapt that check,
> > instead. (Or was the scsw_is_solicited() check supposed to catch that?
> > As said, too tired right now...)
>
> I had looked at the (un)solicited bits at one point, and saw very few
> unsolicited interrupts. The ones that did show up didn't appear to
> affect things in the way that would cause the problems I'm seeing.
Ok, so that check is hopefully fine.
>
> As for is_final... That POPS table states that for "status pending
> [alone] after termination of HALT or CLEAR ... cpa is unpredictable",
> which is what happens here. In the example above, the cpa is the same
> as the previous (successful) interrupt, and thus unrelated to the
> current chain. Perhaps is_final needs to check that the function
> control in the interrupt is for a start?
I think our reasoning last time we discussed this function was that we
only are in CP_PENDING if we actually did a ssch previously. Now, if we
do a hsch/csch before we got final status for the program started by
the ssch, we don't move out of the CP_PENDING, but the cpa still might
not be what we're looking for. So, we should probably check that we
have only the start function indicated in the fctl.
But if we do that, we still have a chain allocated for something that
has already been terminated... how do we find the right chain to clean
up, if needed?
