On Mon, 13 Jan 2020 17:06:05 +0100 David Hildenbrand <david@xxxxxxxxxx> wrote: [...] > >>> this would be solved by adding special logic to the pgm interrupt > >>> handler (as we have discussed in your previous email) > >>> > >> > >> I see, so the issue should hold for all SCLP checks where we don't > >> expect an exception ... hmmm > > > > which is why my wrapper in the unit test is so complicated :) > > > > so .... if we would implement my suggestion (if we get an exception > on a servc instruction, clear sclp_busy) that code would get > simplified as well? :) sure, as I said, that can be done. The question is if we really want to change something in the interrupt handler (shared by all s390x unit tests) just for the benefit of this one unit test. Also consider that the changes to the interrupt handler would not necessarily be trivial. i.e. you need to check that the origin of the pgm interrupt is a SERVC instruction, and then act accordingly.
