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 v1 0/3] drm/xe/vf: Post-migration recovery of GGTT nodes and CTB
Date: Sat, 16 Nov 2024 02:27:52 +0100 [thread overview]
Message-ID: <20241116012755.2297439-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
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_gt_sriov_vf.c | 177 ++++++++++++++++++++++
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 | 144 ++++++++++++++++++
drivers/gpu/drm/xe/xe_guc_ct.h | 2 +
drivers/gpu/drm/xe/xe_sriov_vf.c | 26 ++++
include/drm/drm_mm.h | 19 +++
7 files changed, 371 insertions(+)
--
2.25.1
next reply other threads:[~2024-11-16 1:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 1:27 Tomasz Lis [this message]
2024-11-16 1:27 ` [PATCH v1 1/3] drm/drm_mm: Safe macro for iterating through nodes in range Tomasz Lis
2024-11-16 1:27 ` [PATCH v1 2/3] drm/xe/sriov: Shifting GGTT area post migration Tomasz Lis
2024-11-16 1:27 ` [PATCH v1 3/3] drm/xe/vf: Fixup CTB send buffer messages after migration Tomasz Lis
2024-11-16 1:37 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery of GGTT nodes and CTB Patchwork
2024-11-16 1:37 ` ✗ CI.checkpatch: warning " Patchwork
2024-11-16 1:38 ` ✗ CI.KUnit: 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=20241116012755.2297439-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