diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2017-05-18 10:46:18 +0100 |
|---|---|---|
| committer | Chris Wilson <chris@chris-wilson.co.uk> | 2017-06-14 14:06:22 +0100 |
| commit | 9ee82d783eef3177928a586c1df3f08d9ced72a8 (patch) | |
| tree | c83d2274ec4f3a615243f421bcb5b4ebfeed8d63 /include/uapi/drm | |
| parent | 290271de34f6c22ec2337e3293224575459747d6 (diff) | |
| download | linux-stable-9ee82d783eef3177928a586c1df3f08d9ced72a8.tar.gz linux-stable-9ee82d783eef3177928a586c1df3f08d9ced72a8.tar.bz2 linux-stable-9ee82d783eef3177928a586c1df3f08d9ced72a8.zip | |
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
Diffstat (limited to 'include/uapi/drm')
0 files changed, 0 insertions, 0 deletions