On Wed, 25 Apr 2018 13:06:31 +0200 Halil Pasic <pasic@xxxxxxxxxxxxx> wrote: > On 04/25/2018 08:57 AM, Cornelia Huck wrote: > >> AFAIU this will be the problem of the person implementing the clear > >> and the halt for vfio-ccw. I.e. it's a non-problem right now. > > Well, that person is me:) I will post some RFC Real Soon Now if I stop > > getting sidetracked... > > > > Makes sense. It should be fine either way AFAIU. > > CSCH, more precisely the clear function is supposed to clear the > interruption request(s) too. But I guess there is no way of the CP to > identify an I/O interrupt that should have been cleared -- that is catch > us disrespecting the architecture. I can't think of a way to establish > must happen before relationship... > > But discarding the first interrupt and delivering just one for the CSCH > is fine too for the same reason. Yes, both work. The calling code in the guest has to be able to handle both anyway, since both can happen on real hardware as well (with a smaller race window). -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
