Quoting Chris Wilson (2018-03-02 14:32:42) > As we make preparations to reset the GPU state, we assume that the GPU > is hung and will not advance. Make this assumption more explicit by > setting the STOP_RING bit on the engines as part of our early reset > preparations. I had to drop this one as it causes a CS arbitration event (i.e. context switch) when the CS parser hits the STOP_RING. As we were doing the stop prior to disabling the tasklet, this meant we were handling a spurious interrupt. Note this means that we are generating spurious interrupts prior to the reset currently, just we are effectively masking them :) As for the problem it was trying to solve? I am thinking along the lines of more set-wedge races that used to be prevented by the stop_machine(). -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
