On Tue, Sep 30, 2014 at 04:58:54PM +0100, Tvrtko Ursulin wrote:
>
>
> On 09/30/2014 03:57 PM, Chris Wilson wrote:
> >On Tue, Sep 30, 2014 at 03:08:02PM +0100, Tvrtko Ursulin wrote:
> >>From: Tvrtko Ursulin
> >>
> >>Write and reads following the block changed use engine specific use counters
> >>
On 09/30/2014 03:57 PM, Chris Wilson wrote:
On Tue, Sep 30, 2014 at 03:08:02PM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Write and reads following the block changed use engine specific use counters
and unless that is matched here force wake use counting goes bad. Same
force wake is a
On Tue, Sep 30, 2014 at 03:08:02PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Write and reads following the block changed use engine specific use counters
> and unless that is matched here force wake use counting goes bad. Same
> force wake is attempted to be taken twice which leads
On Tue, Sep 30, 2014 at 03:08:02PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Write and reads following the block changed use engine specific use counters
> and unless that is matched here force wake use counting goes bad. Same
> force wake is attempted to be taken twice which leads
From: Tvrtko Ursulin
Write and reads following the block changed use engine specific use counters
and unless that is matched here force wake use counting goes bad. Same
force wake is attempted to be taken twice which leads to at least time outs.
NOTE: Depending on feedback from hardware designer
On Thu, Sep 25, 2014 at 01:43:31PM +0100, Tvrtko Ursulin wrote:
>
> On 09/25/2014 01:05 PM, Mika Kuoppala wrote:
> >Damien Lespiau writes:
> >
> >>On Thu, Sep 25, 2014 at 11:17:00AM +0100, Tvrtko Ursulin wrote:
> >>>From: Tvrtko Ursulin
> >>>
> >>>Write and reads following the block changed use
On 09/25/2014 01:05 PM, Mika Kuoppala wrote:
Damien Lespiau writes:
On Thu, Sep 25, 2014 at 11:17:00AM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Write and reads following the block changed use engine specific use counters
and unless that is matched here force wake use counting goes
Damien Lespiau writes:
> On Thu, Sep 25, 2014 at 11:17:00AM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin
>>
>> Write and reads following the block changed use engine specific use counters
>> and unless that is matched here force wake use counting goes bad. Same
>> force wake is attempte
On Thu, Sep 25, 2014 at 11:17:00AM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Write and reads following the block changed use engine specific use counters
> and unless that is matched here force wake use counting goes bad. Same
> force wake is attempted to be taken twice which leads
From: Tvrtko Ursulin
Write and reads following the block changed use engine specific use counters
and unless that is matched here force wake use counting goes bad. Same
force wake is attempted to be taken twice which leads to at least time outs.
Signed-off-by: Tvrtko Ursulin
---
drivers/gpu/dr
10 matches
Mail list logo