Quoting Mika Kuoppala (2018-04-26 11:19:14)
> Chris Wilson writes:
>
> > Quoting Mika Kuoppala (2018-04-24 13:26:11)
> >> Chris Wilson writes:
> >>
> >> > Ideally, we want to atomically flush and disable the tasklet before
> >> > resetting the GPU. At present, we rely on being the only part to
Chris Wilson writes:
> Quoting Mika Kuoppala (2018-04-24 13:26:11)
>> Chris Wilson writes:
>>
>> > Ideally, we want to atomically flush and disable the tasklet before
>> > resetting the GPU. At present, we rely on being the only part to touch
>> > our tasklet and serialisation of the reset proc
Quoting Mika Kuoppala (2018-04-24 13:26:11)
> Chris Wilson writes:
>
> > Ideally, we want to atomically flush and disable the tasklet before
> > resetting the GPU. At present, we rely on being the only part to touch
> > our tasklet and serialisation of the reset process to ensure that we can
> >
Chris Wilson writes:
> Ideally, we want to atomically flush and disable the tasklet before
> resetting the GPU. At present, we rely on being the only part to touch
> our tasklet and serialisation of the reset process to ensure that we can
> suspend the tasklet from the mix of reset/wedge pathways
Ideally, we want to atomically flush and disable the tasklet before
resetting the GPU. At present, we rely on being the only part to touch
our tasklet and serialisation of the reset process to ensure that we can
suspend the tasklet from the mix of reset/wedge pathways. In this patch,
we move the ta
