drm/i915: Use 0 for the unordered context

Browse source

Since commit 078dec3326 ("dma-buf: add dma_fence_get_stub") the 0
fence context became an impossible match as it is used for an always
signaled fence. We can simplify our timeline tracking by knowing that 0
always means no match.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190819184404.24200-1-chris@chris-wilson.co.uk
Link: https://patchwork.freedesktop.org/patch/msgid/20190819175109.5241-1-chris@chris-wilson.co.uk

...

This commit is contained in:

Chris Wilson 2019-08-19 19:44:03 +01:00

parent e1d7b66b81

commit cc3375607d

6 changed files with 5 additions and 16 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

drivers/gpu/drm/i915/gem/i915_gem_clflush.c

View file

7

drivers/gpu/drm/i915/gem/i915_gem_client_blt.c

View file

3

drivers/gpu/drm/i915/gem/i915_gem_fence.c

View file

2

drivers/gpu/drm/i915/i915_drv.h

View file

2

drivers/gpu/drm/i915/i915_gem.c

View file

4

drivers/gpu/drm/i915/i915_request.c

View file