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>
Subject: [PATCH v3 0/4] drm/xe/vf: Post-migration recovery worker basis
Date: Fri, 27 Sep 2024 00:20:00 +0200 [thread overview]
Message-ID: <20240926222004.2462345-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 introduces a post-migration recovery worker, executed
after migration to perform fixups.
Specific fixups will be added later in further series.
v2: renamed and moved functions, updated logged messages, removed
unused includes, used anon struct, keeping pm ref during whole
recovery, skip handshake, style fixes (Michal)
v3: ordering, kerneldoc, asserts, debug messages, on_all_tiles ->
on_all_gts, switched 'err' and 'ret' (Michal)
Tomasz Lis (4):
drm/xe/vf: React to MIGRATED interrupt
drm/xe/vf: Send RESFIX_DONE message at end of VF restore
drm/xe/vf: Start post-migration fixups with provisinoning query
drm/xe/vf: Defer fixups if migrated twice fast
drivers/gpu/drm/xe/Makefile | 3 +-
.../gpu/drm/xe/abi/guc_actions_sriov_abi.h | 38 +++++
drivers/gpu/drm/xe/xe_device_types.h | 2 +
drivers/gpu/drm/xe/xe_gt_sriov_vf.c | 56 ++++++
drivers/gpu/drm/xe/xe_gt_sriov_vf.h | 2 +
drivers/gpu/drm/xe/xe_guc.c | 14 +-
drivers/gpu/drm/xe/xe_memirq.c | 3 +
drivers/gpu/drm/xe/xe_sriov.c | 4 +
drivers/gpu/drm/xe/xe_sriov_types.h | 16 ++
drivers/gpu/drm/xe/xe_sriov_vf.c | 160 ++++++++++++++++++
drivers/gpu/drm/xe/xe_sriov_vf.h | 14 ++
11 files changed, 310 insertions(+), 2 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_sriov_vf.c
create mode 100644 drivers/gpu/drm/xe/xe_sriov_vf.h
--
2.25.1
next reply other threads:[~2024-09-26 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 22:20 Tomasz Lis [this message]
2024-09-26 22:20 ` [PATCH v3 1/4] drm/xe/vf: React to MIGRATED interrupt Tomasz Lis
2024-09-26 22:20 ` [PATCH v3 2/4] drm/xe/vf: Send RESFIX_DONE message at end of VF restore Tomasz Lis
2024-09-26 22:20 ` [PATCH v3 3/4] drm/xe/vf: Start post-migration fixups with provisinoning query Tomasz Lis
2024-09-26 22:20 ` [PATCH v3 4/4] drm/xe/vf: Defer fixups if migrated twice fast Tomasz Lis
2024-09-26 22:26 ` ✓ CI.Patch_applied: success for drm/xe/vf: Post-migration recovery worker basis (rev3) Patchwork
2024-09-26 22:26 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-26 22:27 ` ✓ CI.KUnit: success " Patchwork
2024-09-26 22:32 ` ✗ CI.Build: 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=20240926222004.2462345-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 \
/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