On Wed, 24 May 2017, Tvrtko Ursulin wrote:
> On 23/05/2017 12:30, Jani Nikula wrote:
>> On Tue, 23 May 2017, Tvrtko Ursulin wrote:
>>> On 23/05/2017 10:56, Jani Nikula wrote:
On Tue, 23 May 2017, Chris Wilson wrote:
> On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
>
On 23/05/2017 12:30, Jani Nikula wrote:
On Tue, 23 May 2017, Tvrtko Ursulin wrote:
On 23/05/2017 10:56, Jani Nikula wrote:
On Tue, 23 May 2017, Chris Wilson wrote:
On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Waiting for engines needs to happen eve
Your patch also fixes the original warning reported in:
https://lkml.org/lkml/2017/5/21/1
Signed-off-by: Nick Desaulniers
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
On Tue, 23 May 2017, Tvrtko Ursulin wrote:
> On 23/05/2017 10:56, Jani Nikula wrote:
>> On Tue, 23 May 2017, Chris Wilson wrote:
>>> On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Waiting for engines needs to happen even in the non-debug build
On 23/05/2017 12:07, Chris Wilson wrote:
On Tue, May 23, 2017 at 11:51:46AM +0100, Tvrtko Ursulin wrote:
On 23/05/2017 11:30, Chris Wilson wrote:
On Tue, May 23, 2017 at 11:09:17AM +0100, Chris Wilson wrote:
On Tue, May 23, 2017 at 10:36:34AM +0100, Chris Wilson wrote:
On Tue, May 23, 2017
On Tue, May 23, 2017 at 11:51:46AM +0100, Tvrtko Ursulin wrote:
>
> On 23/05/2017 11:30, Chris Wilson wrote:
> >On Tue, May 23, 2017 at 11:09:17AM +0100, Chris Wilson wrote:
> >>On Tue, May 23, 2017 at 10:36:34AM +0100, Chris Wilson wrote:
> >>>On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursu
On 23/05/2017 11:30, Chris Wilson wrote:
On Tue, May 23, 2017 at 11:09:17AM +0100, Chris Wilson wrote:
On Tue, May 23, 2017 at 10:36:34AM +0100, Chris Wilson wrote:
On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Waiting for engines needs to happen even
On Tue, May 23, 2017 at 11:09:17AM +0100, Chris Wilson wrote:
> On Tue, May 23, 2017 at 10:36:34AM +0100, Chris Wilson wrote:
> > On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
> > > From: Tvrtko Ursulin
> > >
> > > Waiting for engines needs to happen even in the non-debug builds
On Tue, May 23, 2017 at 10:36:34AM +0100, Chris Wilson wrote:
> On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
> > From: Tvrtko Ursulin
> >
> > Waiting for engines needs to happen even in the non-debug builds
> > so it is incorrect to wrap it in a GEM_WARN_ON.
> >
> > Call it un
On 23/05/2017 10:56, Jani Nikula wrote:
On Tue, 23 May 2017, Chris Wilson wrote:
On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Waiting for engines needs to happen even in the non-debug builds
so it is incorrect to wrap it in a GEM_WARN_ON.
Call it unc
On Tue, 23 May 2017, Chris Wilson wrote:
> On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin
>>
>> Waiting for engines needs to happen even in the non-debug builds
>> so it is incorrect to wrap it in a GEM_WARN_ON.
>>
>> Call it unconditionally and add GEM_
On Tue, May 23, 2017 at 10:45:44AM +0100, Tvrtko Ursulin wrote:
>
> On 23/05/2017 10:29, Chris Wilson wrote:
> >On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
> >>From: Tvrtko Ursulin
> >>
> >>Waiting for engines needs to happen even in the non-debug builds
> >>so it is incorrect
On 23/05/2017 10:29, Chris Wilson wrote:
On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Waiting for engines needs to happen even in the non-debug builds
so it is incorrect to wrap it in a GEM_WARN_ON.
Call it unconditionally and add GEM_WARN so that the
On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Waiting for engines needs to happen even in the non-debug builds
> so it is incorrect to wrap it in a GEM_WARN_ON.
>
> Call it unconditionally and add GEM_WARN so that the debug
> warning can still be emit
On Tue, May 23, 2017 at 10:19:31AM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Waiting for engines needs to happen even in the non-debug builds
> so it is incorrect to wrap it in a GEM_WARN_ON.
>
> Call it unconditionally and add GEM_WARN so that the debug
> warning can still be emit
From: Tvrtko Ursulin
Waiting for engines needs to happen even in the non-debug builds
so it is incorrect to wrap it in a GEM_WARN_ON.
Call it unconditionally and add GEM_WARN so that the debug
warning can still be emitted when things go bad.
Signed-off-by: Tvrtko Ursulin
Fixes: 25112b64b3d2 ("
16 matches
Mail list logo