Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2016-01-04 Thread Dave Gordon
On 04/01/16 14:20, Chris Wilson wrote: On Mon, Jan 04, 2016 at 02:09:53PM +, Dave Gordon wrote: On 04/01/16 13:02, Dave Gordon wrote: On 04/01/16 11:26, Chris Wilson wrote: On Mon, Jan 04, 2016 at 11:16:04AM +, Dave Gordon wrote: On 14/12/15 15:11, Chris Wilson wrote: On Mon, Dec 14,

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2016-01-04 Thread Chris Wilson
On Mon, Jan 04, 2016 at 02:09:53PM +, Dave Gordon wrote: > On 04/01/16 13:02, Dave Gordon wrote: > >On 04/01/16 11:26, Chris Wilson wrote: > >>On Mon, Jan 04, 2016 at 11:16:04AM +, Dave Gordon wrote: > >>>On 14/12/15 15:11, Chris Wilson wrote: > On Mon, Dec 14, 2015 at 02:59:30PM +,

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2016-01-04 Thread Dave Gordon
On 04/01/16 13:02, Dave Gordon wrote: On 04/01/16 11:26, Chris Wilson wrote: On Mon, Jan 04, 2016 at 11:16:04AM +, Dave Gordon wrote: On 14/12/15 15:11, Chris Wilson wrote: On Mon, Dec 14, 2015 at 02:59:30PM +, Tvrtko Ursulin wrote: Hi, On 11/12/15 11:33, Chris Wilson wrote: Now th

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2016-01-04 Thread Chris Wilson
On Mon, Jan 04, 2016 at 01:02:25PM +, Dave Gordon wrote: > On 04/01/16 11:26, Chris Wilson wrote: > >On Mon, Jan 04, 2016 at 11:16:04AM +, Dave Gordon wrote: > >>On 14/12/15 15:11, Chris Wilson wrote: > >>>On Mon, Dec 14, 2015 at 02:59:30PM +, Tvrtko Ursulin wrote: > > Hi, > >>

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2016-01-04 Thread Dave Gordon
On 04/01/16 11:26, Chris Wilson wrote: On Mon, Jan 04, 2016 at 11:16:04AM +, Dave Gordon wrote: On 14/12/15 15:11, Chris Wilson wrote: On Mon, Dec 14, 2015 at 02:59:30PM +, Tvrtko Ursulin wrote: Hi, On 11/12/15 11:33, Chris Wilson wrote: Now that we have split out the seqno-barrier

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2016-01-04 Thread Chris Wilson
On Mon, Jan 04, 2016 at 11:16:04AM +, Dave Gordon wrote: > On 14/12/15 15:11, Chris Wilson wrote: > >On Mon, Dec 14, 2015 at 02:59:30PM +, Tvrtko Ursulin wrote: > >> > >>Hi, > >> > >>On 11/12/15 11:33, Chris Wilson wrote: > >>>Now that we have split out the seqno-barrier from the > >>>engin

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2016-01-04 Thread Dave Gordon
On 14/12/15 15:11, Chris Wilson wrote: On Mon, Dec 14, 2015 at 02:59:30PM +, Tvrtko Ursulin wrote: Hi, On 11/12/15 11:33, Chris Wilson wrote: Now that we have split out the seqno-barrier from the engine->get_seqno() callback itself, we can move the users of the seqno-barrier to the requir

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2015-12-14 Thread Chris Wilson
On Mon, Dec 14, 2015 at 02:59:30PM +, Tvrtko Ursulin wrote: > > Hi, > > On 11/12/15 11:33, Chris Wilson wrote: > >Now that we have split out the seqno-barrier from the > >engine->get_seqno() callback itself, we can move the users of the > >seqno-barrier to the required callsites simplifying t

Re: [Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2015-12-14 Thread Tvrtko Ursulin
Hi, On 11/12/15 11:33, Chris Wilson wrote: Now that we have split out the seqno-barrier from the engine->get_seqno() callback itself, we can move the users of the seqno-barrier to the required callsites simplifying the common code and making the required workaround handling much more explicit.

[Intel-gfx] [PATCH 17/32] drm/i915: Remove the lazy_coherency parameter from request-completed?

2015-12-11 Thread Chris Wilson
Now that we have split out the seqno-barrier from the engine->get_seqno() callback itself, we can move the users of the seqno-barrier to the required callsites simplifying the common code and making the required workaround handling much more explicit. Signed-off-by: Chris Wilson --- drivers/gpu/