Re: [Intel-gfx] [PATCH 7/7] drm/i915: Lazily unbind vma on close

2018-04-27 Thread Chris Wilson
Quoting Tvrtko Ursulin (2018-04-27 16:38:47) > > On 26/04/2018 18:49, Chris Wilson wrote: > > diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c > > b/drivers/gpu/drm/i915/i915_gem_execbuffer.c > > index c74f5df3fb5a..f627a8c47c58 100644 > > --- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c >

Re: [Intel-gfx] [PATCH 7/7] drm/i915: Lazily unbind vma on close

2018-04-27 Thread Tvrtko Ursulin
On 26/04/2018 18:49, Chris Wilson wrote: When userspace is passing around swapbuffers using DRI, we frequently have to open and close the same object in the foreign address space. This shows itself as the same object being rebound at roughly 30fps (with a second object also being rebound at 30fp

[Intel-gfx] [PATCH 7/7] drm/i915: Lazily unbind vma on close

2018-04-26 Thread Chris Wilson
When userspace is passing around swapbuffers using DRI, we frequently have to open and close the same object in the foreign address space. This shows itself as the same object being rebound at roughly 30fps (with a second object also being rebound at 30fps), which involves us having to rewrite the

[Intel-gfx] [PATCH 7/7] drm/i915: Lazily unbind vma on close

2018-04-25 Thread Chris Wilson
When userspace is passing around swapbuffers using DRI, we frequently have to open and close the same object in the foreign address space. This shows itself as the same object being rebound at roughly 30fps (with a second object also being rebound at 30fps), which involves us having to rewrite the