[PATCH v2 0/2] drm/xe/vf: New approach for post-migration LRC fixups

[Tomasz Lis <tomasz.lis@intel.com>]

The current approach to LRC recovery requires caution from developers
when modifying any LRC-related code. More flexible solution may allow
to avoid future troubles.

The current code also includes LRC creation repeat which looks a bit
suspicious - it was developed without detailed knowledge of which
part of LRC creation requires a repeat. Now after extensive debug we
know that the repeat is only required for BO mapping, and actually
all BOs should be protected, not only the ones storing LRCs.

This fixes a very rare bug where BO would be incorrectly created
during migration resulting in CAT error generated by GPU. Chances
of triggering this error were well below 0.1%.

v2: A rebase after 6 months, with adjustments to current source.

Signed-off-by: Tomasz Lis <tomasz.lis@intel.com>

Tomasz Lis (2):
  drm/xe/vf: Late fixups of LRCs after VF migration
  drm/xe: After VF migration, repeat BO mapping in progress

 drivers/gpu/drm/xe/xe_exec_queue.c        | 55 +++++++++++++----------
 drivers/gpu/drm/xe/xe_exec_queue.h        |  2 +-
 drivers/gpu/drm/xe/xe_ggtt.c              | 17 +++++++
 drivers/gpu/drm/xe/xe_gt_sriov_vf.c       |  6 +--
 drivers/gpu/drm/xe/xe_gt_sriov_vf_types.h |  2 +
 drivers/gpu/drm/xe/xe_guc_submit.c        | 35 +++------------
 drivers/gpu/drm/xe/xe_guc_submit.h        |  2 -
 7 files changed, 60 insertions(+), 59 deletions(-)

-- 
2.43.0