Oops, sent out the wrong patch, pls disregard.
-Daniel
On Thu, Jul 20, 2017 at 10:14 PM, Daniel Vetter wrote:
> ... at least not in that place, because this can also fire for
> requests which have completed. Which then hits the assert in
> dma_fence_set_error.
>
> Since
... at least not in that place, because this can also fire for
requests which have completed. Which then hits the assert in
dma_fence_set_error.
Since I'm not really clear what should be done here I pinged Chris,
and he suggested we simply remove this for now.
Found while stress-testing gpu
Quoting Daniel Vetter (2017-07-20 18:59:01)
> ... at least not in that place, because this can also fire for
> requests which have completed. Which then hits the assert in
> dma_fence_set_error.
>
> Since I'm not really clear what should be done here I pinged Chris,
> and he suggested we simply
... at least not in that place, because this can also fire for
requests which have completed. Which then hits the assert in
dma_fence_set_error.
Since I'm not really clear what should be done here I pinged Chris,
and he suggested we simply remove this for now.
Found while stress-testing gpu