On Fri, Jun 17, 2016 at 08:09:05AM +0100, Arun Siluvery wrote: > To resume execution after engine reset we resubmit the context and this > needs to be treated differently otherwise we would count it as a completely > new submission. This change modifies the submission path to account for > this. > > During resubmission we only submit the head request that caused the hang, > once this is done then we continue with the normally submission of two > contexts at a time. The intention is to restore the submission state at the > time of hang. Why do we want to resubmit the hanging request (with HEAD increment by a couple of dwords)? Kill the job, move on. How quickly do you decide to actually abandon the request? -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
