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>,
"Satyanarayana K V P" <satyanarayana.k.v.p@intel.com>
Subject: [PATCH v3 0/5] drm/xe/vf: Minor fixes to post-migration recovery
Date: Thu, 16 Oct 2025 14:05:06 +0200 [thread overview]
Message-ID: <20251016120511.856792-1-tomasz.lis@intel.com> (raw)
The series contains few minor fixes, mostly related to VF driver probe.
The fixes are not strictly related, but all go under VF migration category.
v2: Add fixing the currently broken GuC ABI check
v3: Add separation of xe_sriov_vf_ccs_migration_bb_needed()
Tomasz Lis (5):
drm/xe/vf: Helper for telling whether CCS migration BBs are needed
drm/xe/vf: Fix GuC FW check for VF migration support
drm/xe/vf: Skip fixups on VF migration before getting GGTT info
drm/xe: Assert that VF will never use fixed placement of BOs
drm/xe/vf: Do not disable VF migration on ATS-M
drivers/gpu/drm/xe/xe_bo.c | 6 ++++
drivers/gpu/drm/xe/xe_gt_sriov_vf.c | 53 ++++++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_gt_sriov_vf.h | 1 +
drivers/gpu/drm/xe/xe_guc.c | 2 ++
drivers/gpu/drm/xe/xe_sriov_vf.c | 15 +++-----
drivers/gpu/drm/xe/xe_sriov_vf_ccs.c | 15 +++++++-
drivers/gpu/drm/xe/xe_sriov_vf_ccs.h | 2 ++
7 files changed, 82 insertions(+), 12 deletions(-)
--
2.25.1
next reply other threads:[~2025-10-16 12:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 12:05 Tomasz Lis [this message]
2025-10-16 12:05 ` [PATCH v3 1/5] drm/xe/vf: Helper for telling whether CCS migration BBs are needed Tomasz Lis
2025-10-16 19:57 ` Michal Wajdeczko
2025-10-16 21:51 ` Lis, Tomasz
2025-10-16 12:05 ` [PATCH v3 2/5] drm/xe/vf: Fix GuC FW check for VF migration support Tomasz Lis
2025-10-16 21:55 ` Michal Wajdeczko
2025-10-17 15:31 ` Lis, Tomasz
2025-10-17 15:40 ` Michal Wajdeczko
2025-10-16 12:05 ` [PATCH v3 3/5] drm/xe/vf: Skip fixups on VF migration before getting GGTT info Tomasz Lis
2025-10-16 22:20 ` Michal Wajdeczko
2025-10-20 19:30 ` Lis, Tomasz
2025-10-16 12:05 ` [PATCH v3 4/5] drm/xe: Assert that VF will never use fixed placement of BOs Tomasz Lis
2025-10-16 12:05 ` [PATCH v3 5/5] drm/xe/vf: Do not disable VF migration on ATS-M Tomasz Lis
2025-10-16 22:25 ` Michal Wajdeczko
2025-10-20 19:22 ` Lis, Tomasz
2025-10-16 12:11 ` ✓ CI.KUnit: success for drm/xe/vf: Minor fixes to post-migration recovery (rev3) Patchwork
2025-10-16 12:57 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-17 8:23 ` ✗ 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=20251016120511.856792-1-tomasz.lis@intel.com \
--to=tomasz.lis@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=piotr.piorkowski@intel.com \
--cc=satyanarayana.k.v.p@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