On Mon, 19 Aug 2019 at 17:45, Chris Wilson <[email protected]> wrote: > > Since commit 078dec3326e2 ("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 <[email protected]> Reviewed-by: Matthew Auld <[email protected]> _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
- [Intel-gfx] [PATCH 09/10] drm/i915: Make shrink/unshrink be a... Chris Wilson
- [Intel-gfx] [PATCH 10/10] drm/i915: Be defensive when startin... Chris Wilson
- [Intel-gfx] [PATCH 06/10] drm/i915: Only track bound elements... Chris Wilson
- [Intel-gfx] [PATCH 05/10] drm/i915: Track ggtt fence reservat... Chris Wilson
- [Intel-gfx] [PATCH 04/10] drm/i915: Replace PIN_NONFAULT with... Chris Wilson
- [Intel-gfx] [PATCH 08/10] drm/i915: Replace i915_vma_put_fenc... Chris Wilson
- [Intel-gfx] [PATCH 07/10] drm/i915: Pull obj->userfault tr... Chris Wilson
- [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting w... Patchwork
- [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [01... Patchwork
- Re: [Intel-gfx] [PATCH 01/10] drm/i915: Use 0 for the unorder... Matthew Auld
