Re: [Intel-gfx] [PATCH] drm/i915: Move VMAs to inactive as request are retired

2015-11-26 Thread Daniel Vetter
On Thu, Nov 26, 2015 at 02:07:57PM +, Tvrtko Ursulin wrote: > > On 26/11/15 10:01, Daniel Vetter wrote: > >On Wed, Nov 25, 2015 at 10:16:37AM +, Tvrtko Ursulin wrote: > >> > >>On 24/11/15 17:47, Daniel Vetter wrote: > >>>On Mon, Nov 23, 2015 at 03:12:35PM +, Tvrtko Ursulin wrote: > >>>

Re: [Intel-gfx] [PATCH] drm/i915: Move VMAs to inactive as request are retired

2015-11-26 Thread Tvrtko Ursulin
On 26/11/15 10:01, Daniel Vetter wrote: On Wed, Nov 25, 2015 at 10:16:37AM +, Tvrtko Ursulin wrote: On 24/11/15 17:47, Daniel Vetter wrote: On Mon, Nov 23, 2015 at 03:12:35PM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Current code moves _any_ VMA to the inactive list only when _

Re: [Intel-gfx] [PATCH] drm/i915: Move VMAs to inactive as request are retired

2015-11-26 Thread Chris Wilson
On Mon, Nov 23, 2015 at 03:12:35PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Current code moves _any_ VMA to the inactive list only when > _all_ rendering on an object (so from any context or VM) has > been completed. > > This creates an un-natural situation where the context (and

Re: [Intel-gfx] [PATCH] drm/i915: Move VMAs to inactive as request are retired

2015-11-26 Thread Daniel Vetter
On Wed, Nov 25, 2015 at 10:16:37AM +, Tvrtko Ursulin wrote: > > On 24/11/15 17:47, Daniel Vetter wrote: > >On Mon, Nov 23, 2015 at 03:12:35PM +, Tvrtko Ursulin wrote: > >>From: Tvrtko Ursulin > >> > >>Current code moves _any_ VMA to the inactive list only when > >>_all_ rendering on an ob

Re: [Intel-gfx] [PATCH] drm/i915: Move VMAs to inactive as request are retired

2015-11-25 Thread Tvrtko Ursulin
On 24/11/15 17:47, Daniel Vetter wrote: On Mon, Nov 23, 2015 at 03:12:35PM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Current code moves _any_ VMA to the inactive list only when _all_ rendering on an object (so from any context or VM) has been completed. This creates an un-natural sit

Re: [Intel-gfx] [PATCH] drm/i915: Move VMAs to inactive as request are retired

2015-11-24 Thread Daniel Vetter
On Mon, Nov 23, 2015 at 03:12:35PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Current code moves _any_ VMA to the inactive list only when > _all_ rendering on an object (so from any context or VM) has > been completed. > > This creates an un-natural situation where the context (and

[Intel-gfx] [PATCH] drm/i915: Move VMAs to inactive as request are retired

2015-11-23 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Current code moves _any_ VMA to the inactive list only when _all_ rendering on an object (so from any context or VM) has been completed. This creates an un-natural situation where the context (and VM) destructors can run with VMAs still on the respective active list. Change