Intel-XE Archive on 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>
Subject: [PATCH v3 0/3] drm/xe/vf: Post-migration recovery of GGTT nodes and CTB
Date: Sat, 23 Nov 2024 04:13:29 +0100	[thread overview]
Message-ID: <20241123031333.3435414-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 drm_mm nodes which represent GGTT allocations
* for fixing content of outgoing CTB buffer

v2: Fixed missing include, made checkpatch happy
v3: Moved some functs to xe_ggtt.c; moved shift computation to just
  after querying; improved documentation; switched some warns to asserts;
  skipping fixups when GGTT shift eq 0; iterating through tiles rather
  than gts; fixes in log messages

Tomasz Lis (3):
  drm/drm_mm: Safe macro for iterating through nodes in range
  drm/xe/sriov: Shifting GGTT area post migration
  drm/xe/vf: Fixup CTB send buffer messages after migration

 drivers/gpu/drm/xe/xe_ggtt.c              | 139 ++++++++++++++++++++
 drivers/gpu/drm/xe/xe_ggtt.h              |   3 +
 drivers/gpu/drm/xe/xe_gt_sriov_vf.c       |  25 ++++
 drivers/gpu/drm/xe/xe_gt_sriov_vf.h       |   1 +
 drivers/gpu/drm/xe/xe_gt_sriov_vf_types.h |   2 +
 drivers/gpu/drm/xe/xe_guc_ct.c            | 148 ++++++++++++++++++++++
 drivers/gpu/drm/xe/xe_guc_ct.h            |   2 +
 drivers/gpu/drm/xe/xe_sriov_vf.c          |  38 ++++++
 include/drm/drm_mm.h                      |  19 +++
 9 files changed, 377 insertions(+)

-- 
2.25.1


             reply	other threads:[~2024-11-23  3:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-23  3:13 Tomasz Lis [this message]
2024-11-23  3:13 ` [PATCH v3 1/3] drm/drm_mm: Safe macro for iterating through nodes in range Tomasz Lis
2024-11-27 21:31   ` Michal Wajdeczko
2024-11-23  3:13 ` [PATCH v3 2/3] drm/xe/sriov: Shifting GGTT area post migration Tomasz Lis
2024-11-27 22:30   ` Michal Wajdeczko
2024-12-03 18:22     ` Lis, Tomasz
2024-11-23  3:13 ` [PATCH v3 3/3] drm/xe/vf: Fixup CTB send buffer messages after migration Tomasz Lis
2024-11-27 23:21   ` Michal Wajdeczko
2024-12-03 18:21     ` Lis, Tomasz
2024-11-23  4:00 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery of GGTT nodes and CTB (rev3) Patchwork
2024-11-23  4:00 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-23  4:02 ` ✓ CI.KUnit: success " Patchwork
2024-11-23  4:20 ` ✓ CI.Build: " Patchwork
2024-11-23  4:22 ` ✓ CI.Hooks: " Patchwork
2024-11-23  4:24 ` ✗ CI.checksparse: warning " Patchwork
2024-11-23  4:45 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-24 14:04 ` ✗ Xe.CI.Full: failure " 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=20241123031333.3435414-1-tomasz.lis@intel.com \
    --to=tomasz.lis@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox