[PATCH 0/1] Fix serialization on burst of unbinds

[Matthew Brost <matthew.brost@intel.com>]

Attempting to resolve part of [1]; the patch should explain the details
of this solution.

Other options have been discussed, including not exporting TLB
invalidation fences to user space, or using TLB invalidation fences to
enforce ordering on the bind queue, rather than simply attaching TLB
invalidations to dma-resv, which blocks reclaim. I’ve implemented this
approach, and it appears to have the same effect as this patch. However,
I can't confidently reason that it won't violate queue fence ordering
rules. If desired, this alternative solution can also be posted for
discussion.

Matt

[1] https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6047

Matthew Brost (1):
  drm/xe: Avoid serializing unbind jobs on prior TLB invalidations

 drivers/gpu/drm/xe/xe_exec.c          |  3 +-
 drivers/gpu/drm/xe/xe_exec_queue.c    | 18 +++++++++--
 drivers/gpu/drm/xe/xe_exec_queue.h    |  3 +-
 drivers/gpu/drm/xe/xe_pt.c            | 15 +++++++--
 drivers/gpu/drm/xe/xe_sched_job.c     | 44 ++++++++++++++++++++++++++-
 drivers/gpu/drm/xe/xe_sched_job.h     |  7 ++++-
 drivers/gpu/drm/xe/xe_tlb_inval_job.c | 14 +++++++++
 drivers/gpu/drm/xe/xe_tlb_inval_job.h |  2 ++
 8 files changed, 98 insertions(+), 8 deletions(-)

-- 
2.34.1