diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2018-03-07 17:13:03 +0000 |
---|---|---|
committer | Rodrigo Vivi <rodrigo.vivi@intel.com> | 2018-03-12 11:24:44 -0700 |
commit | 82813ba9b4b31cd445a2ec1a1404de6e78f32b35 (patch) | |
tree | 52c2bf5134ef004c41dda0b13f8a422fb42dffba /net/ipv4/udplite.c | |
parent | e8cd7143e269ab58344ff10d9729da144e17fed2 (diff) | |
download | op-kernel-dev-82813ba9b4b31cd445a2ec1a1404de6e78f32b35.zip op-kernel-dev-82813ba9b4b31cd445a2ec1a1404de6e78f32b35.tar.gz |
drm/i915: Only prune fences after wait-for-all
Currently, we only allow ourselves to prune the fences so long as
all the waits completed (i.e. all the fences we checked were signaled),
and that the reservation snapshot did not change across the wait.
However, if we only waited for a subset of the reservation object, i.e.
just waiting for the last writer to complete as opposed to all readers
as well, then we would erroneously conclude we could prune the fences as
indeed although all of our waits were successful, they did not represent
the totality of the reservation object.
v2: We only need to check the shared fences due to construction (i.e.
all of the shared fences will be later than the exclusive fence, if
any).
Fixes: e54ca9774777 ("drm/i915: Remove completed fences after a wait")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20180307171303.29466-1-chris@chris-wilson.co.uk
(cherry picked from commit fa73055b8442c97b3ba7cd0aa57cd2ad32124201)
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'net/ipv4/udplite.c')
0 files changed, 0 insertions, 0 deletions