Quoting Jani Nikula (2017-11-21 10:23:44)
> On Tue, 21 Nov 2017, Chris Wilson wrote:
> > Quoting Jani Nikula (2017-11-21 09:57:30)
> >> On Mon, 20 Nov 2017, Chris Wilson wrote:
> >> > I should have admitted defeat long ago as there has been a rare but
> >> > persistent error on Sandybridge where
On Tue, 21 Nov 2017, Chris Wilson wrote:
> Quoting Jani Nikula (2017-11-21 09:57:30)
>> On Mon, 20 Nov 2017, Chris Wilson wrote:
>> > I should have admitted defeat long ago as there has been a rare but
>> > persistent error on Sandybridge where semaphore signaling did not
>> > propagate to the wa
Quoting Jani Nikula (2017-11-21 09:57:30)
> On Mon, 20 Nov 2017, Chris Wilson wrote:
> > I should have admitted defeat long ago as there has been a rare but
> > persistent error on Sandybridge where semaphore signaling did not
> > propagate to the waiter, leading to a GPU hang.
>
> I'm late to th
On Mon, 20 Nov 2017, Chris Wilson wrote:
> I should have admitted defeat long ago as there has been a rare but
> persistent error on Sandybridge where semaphore signaling did not
> propagate to the waiter, leading to a GPU hang.
I'm late to the party, but I think the choice of patch ordering here
I should have admitted defeat long ago as there has been a rare but
persistent error on Sandybridge where semaphore signaling did not
propagate to the waiter, leading to a GPU hang.
With the work on fence signaling for v4.9, the impact of using CPU driven
signaling was greatly reduced wrt to the l
I should have admitted defeat long ago as there has been a rare but
persistent error on Sandybridge where semaphore signaling did not
propagate to the waiter, leading to a GPU hang.
With the work on fence signaling for v4.9, the impact of using CPU driven
signaling was greatly reduced wrt to the l
