Re: [Intel-gfx] [PATCH 08/27] drm/i915/icl: Ringbuffer interrupt handling

2018-02-01 Thread Belgaumkar, Vinay
On 2/1/2018 3:58 PM, Belgaumkar, Vinay wrote: On 1/15/2018 2:38 AM, Tvrtko Ursulin wrote: On 11/01/2018 19:17, Daniele Ceraolo Spurio wrote: On 10/01/18 02:12, Chris Wilson wrote: Quoting Paulo Zanoni (2018-01-09 23:23:17) From: Tvrtko Ursulin Since it is not possible to mask individ

Re: [Intel-gfx] [PATCH 08/27] drm/i915/icl: Ringbuffer interrupt handling

2018-02-01 Thread Belgaumkar, Vinay
On 1/15/2018 2:38 AM, Tvrtko Ursulin wrote: On 11/01/2018 19:17, Daniele Ceraolo Spurio wrote: On 10/01/18 02:12, Chris Wilson wrote: Quoting Paulo Zanoni (2018-01-09 23:23:17) From: Tvrtko Ursulin Since it is not possible to mask individual engine instances and they are all permanently

Re: [Intel-gfx] [PATCH 08/27] drm/i915/icl: Ringbuffer interrupt handling

2018-01-15 Thread Tvrtko Ursulin
On 11/01/2018 19:17, Daniele Ceraolo Spurio wrote: On 10/01/18 02:12, Chris Wilson wrote: Quoting Paulo Zanoni (2018-01-09 23:23:17) From: Tvrtko Ursulin Since it is not possible to mask individual engine instances and they are all permanently unmasked we do not need to do anything for eng

Re: [Intel-gfx] [PATCH 08/27] drm/i915/icl: Ringbuffer interrupt handling

2018-01-11 Thread Daniele Ceraolo Spurio
On 10/01/18 02:12, Chris Wilson wrote: Quoting Paulo Zanoni (2018-01-09 23:23:17) From: Tvrtko Ursulin Since it is not possible to mask individual engine instances and they are all permanently unmasked we do not need to do anything for engine interrupt management. This scares me as we will

Re: [Intel-gfx] [PATCH 08/27] drm/i915/icl: Ringbuffer interrupt handling

2018-01-10 Thread Chris Wilson
Quoting Paulo Zanoni (2018-01-09 23:23:17) > From: Tvrtko Ursulin > > Since it is not possible to mask individual engine instances > and they are all permanently unmasked we do not need to do > anything for engine interrupt management. This scares me as we will more than double our interrupt gen

[Intel-gfx] [PATCH 08/27] drm/i915/icl: Ringbuffer interrupt handling

2018-01-09 Thread Paulo Zanoni
From: Tvrtko Ursulin Since it is not possible to mask individual engine instances and they are all permanently unmasked we do not need to do anything for engine interrupt management. v2: Rebase. v3: Remove gen 11 extra check in logical_render_ring_init. v4: Rebase fixes. v5: Rebase/refactor. v6: