All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Lis <tomasz.lis@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Michał Winiarski" <michal.winiarski@intel.com>,
	"Michał Wajdeczko" <michal.wajdeczko@intel.com>,
	"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>
Subject: [PATCH v2 0/7] drm/xe/vf: Post-migration recovery of queues and jobs
Date: Fri, 16 May 2025 00:18:20 +0200	[thread overview]
Message-ID: <20250515221827.1493032-1-tomasz.lis@intel.com> (raw)

To support VF Migration, it is necessary to do fixups to any
non-virtualized resources. These fixups need to be applied within
VM, on the KMD working with VF.

This series adds two fixup functions to the recovery worker:
* for fixing xe_lrc structs within queues
* for fixing xe_job structs and the commands they emit
It also provides some performance and stability fixes - blocking
submissions and resets while the fixups are being applied.
In case of sub-allocator, it removes the cached GGTT addresses
instead of implementing fixups for them.

v2: Switcghed to update of addresses by xe_lrc_write_ctx_reg()
  to avoid kzalloc(), renamed or moved few functions

Tomasz Lis (7):
  drm/xe/sa: Avoid caching GGTT address within the manager
  drm/xe/vf: Finish RESFIX by reset if CTB not enabled
  drm/xe/vf: Pause submissions during RESFIX fixups
  drm/xe: Block reset while recovering from VF migration
  drm/xe/vf: Rebase HWSP of all contexts after migration
  drm/xe/vf: Rebase MEMIRQ structures for all contexts after migration
  drm/xe/vf: Post migration, repopulate ring area for pending request

 drivers/gpu/drm/xe/xe_exec_queue.c    |  27 +++++++
 drivers/gpu/drm/xe/xe_exec_queue.h    |   4 +
 drivers/gpu/drm/xe/xe_gpu_scheduler.c |  13 ++++
 drivers/gpu/drm/xe/xe_gpu_scheduler.h |   1 +
 drivers/gpu/drm/xe/xe_gt_debugfs.c    |   3 +-
 drivers/gpu/drm/xe/xe_gt_sriov_vf.c   |  10 +++
 drivers/gpu/drm/xe/xe_guc_buf.c       |   2 +-
 drivers/gpu/drm/xe/xe_guc_submit.c    |  91 +++++++++++++++++++++-
 drivers/gpu/drm/xe/xe_guc_submit.h    |   8 ++
 drivers/gpu/drm/xe/xe_lrc.c           |  51 +++++++++++++
 drivers/gpu/drm/xe/xe_lrc.h           |   3 +
 drivers/gpu/drm/xe/xe_sa.c            |   1 -
 drivers/gpu/drm/xe/xe_sa.h            |  15 +++-
 drivers/gpu/drm/xe/xe_sa_types.h      |   1 -
 drivers/gpu/drm/xe/xe_sriov_vf.c      | 105 +++++++++++++++++++++++++-
 drivers/gpu/drm/xe/xe_sriov_vf.h      |   1 +
 16 files changed, 327 insertions(+), 9 deletions(-)

-- 
2.25.1


             reply	other threads:[~2025-05-15 22:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 22:18 Tomasz Lis [this message]
2025-05-15 22:18 ` [PATCH v2 1/7] drm/xe/sa: Avoid caching GGTT address within the manager Tomasz Lis
2025-05-15 22:18 ` [PATCH v2 2/7] drm/xe/vf: Finish RESFIX by reset if CTB not enabled Tomasz Lis
2025-05-15 22:18 ` [PATCH v2 3/7] drm/xe/vf: Pause submissions during RESFIX fixups Tomasz Lis
2025-05-16 17:30   ` Michal Wajdeczko
2025-05-19 23:07     ` Lis, Tomasz
2025-05-15 22:18 ` [PATCH v2 4/7] drm/xe: Block reset while recovering from VF migration Tomasz Lis
2025-05-15 22:18 ` [PATCH v2 5/7] drm/xe/vf: Rebase HWSP of all contexts after migration Tomasz Lis
2025-05-16 17:01   ` Michal Wajdeczko
2025-05-15 22:18 ` [PATCH v2 6/7] drm/xe/vf: Rebase MEMIRQ structures for " Tomasz Lis
2025-05-16 17:15   ` Michal Wajdeczko
2025-05-15 22:18 ` [PATCH v2 7/7] drm/xe/vf: Post migration, repopulate ring area for pending request Tomasz Lis
2025-05-15 22:24 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery of queues and jobs (rev2) Patchwork
2025-05-15 22:25 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-15 22:26 ` ✓ CI.KUnit: success " Patchwork
2025-05-15 22:36 ` ✓ CI.Build: " Patchwork
2025-05-15 22:39 ` ✓ CI.Hooks: " Patchwork
2025-05-15 22:40 ` ✓ CI.checksparse: " Patchwork
2025-05-15 23:03 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-16 14:21 ` ✓ Xe.CI.Full: " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250515221827.1493032-1-tomasz.lis@intel.com \
    --to=tomasz.lis@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=piotr.piorkowski@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.