drm/i915: Reinstate reservation_object zapping for batch_pool objects
authorChris Wilson <chris@chris-wilson.co.uk>
Thu, 18 May 2017 09:46:18 +0000 (10:46 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Wed, 14 Jun 2017 13:06:22 +0000 (14:06 +0100)
commit9ee82d783eef3177928a586c1df3f08d9ced72a8
treec83d2274ec4f3a615243f421bcb5b4ebfeed8d63
parent290271de34f6c22ec2337e3293224575459747d6
drm/i915: Reinstate reservation_object zapping for batch_pool objects

I removed the zapping of the reservation_object->fence array of shared
fences prematurely. We don't yet have the code to zap that array when
retiring the object, and so currently it remains possible to continually
grow the shared array trapping requests when reusing the batch_pool
object across many timelines.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Mika Kuoppala <mika.kuoppala@intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170518094638.5469-4-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/i915_gem_batch_pool.c