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>
Subject: [PATCH v1 0/3] drm/xe/vf: Minor fixes to post-migration recovery
Date: Tue, 14 Oct 2025 02:44:15 +0200 [thread overview]
Message-ID: <20251014004418.378928-1-tomasz.lis@intel.com> (raw)
The series contains 3 fixes:
* Ignore migration recovery request too early during VF driver probe
* Assert that BO never tries to map into GGTT at fixed offset on VFs
* Allow migration on ATS-M in addition to newer platforms
The fixes are not strictly related, but all go under VF migration category.
Tomasz Lis (3):
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 | 12 ++++++++++++
drivers/gpu/drm/xe/xe_sriov_vf.c | 4 ++--
3 files changed, 20 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2025-10-14 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 0:44 Tomasz Lis [this message]
2025-10-14 0:44 ` [PATCH v1 1/3] drm/xe/vf: Skip fixups on VF migration before getting GGTT info Tomasz Lis
2025-10-14 0:44 ` [PATCH v1 2/3] drm/xe: Assert that VF will never use fixed placement of BOs Tomasz Lis
2025-10-14 0:44 ` [PATCH v1 3/3] drm/xe/vf: Do not disable VF migration on ATS-M Tomasz Lis
2025-10-14 1:57 ` ✓ CI.KUnit: success for drm/xe/vf: Minor fixes to post-migration recovery Patchwork
2025-10-14 2:40 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-10-14 10:44 ` ✗ 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=20251014004418.378928-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 \
/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