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>,
	"Matthew Brost" <matthew.brost@intel.com>
Subject: [PATCH v2 4/4] drm/xe/vf: Do not disable VF migration on ATS-M
Date: Wed, 15 Oct 2025 02:27:55 +0200	[thread overview]
Message-ID: <20251015002755.720992-5-tomasz.lis@intel.com> (raw)
In-Reply-To: <20251015002755.720992-1-tomasz.lis@intel.com>

The ATS-M does support VF migration, and it has graphics ver below
the currently allowed range. Experimental support of this platform
should therefore be available.

This change allows experimental VF migration support on ATS-M. It
is also explicitly not allowing ADL, by adding condition on MEMIRQ.
Supporting VF migration through MMIO interrupts would require
some special handling in order to achieve reliability.

v2: Add MEMIRQ condition

Signed-off-by: Tomasz Lis <tomasz.lis@intel.com>
---
 drivers/gpu/drm/xe/xe_sriov_vf.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_sriov_vf.c b/drivers/gpu/drm/xe/xe_sriov_vf.c
index 5fb042c05112..fb2b3d41c610 100644
--- a/drivers/gpu/drm/xe/xe_sriov_vf.c
+++ b/drivers/gpu/drm/xe/xe_sriov_vf.c
@@ -159,10 +159,13 @@ static void vf_migration_init_early(struct xe_device *xe)
 		return vf_disable_migration(xe,
 					    "experimental feature not available on production builds");
 
-	if (GRAPHICS_VER(xe) < 20)
-		return vf_disable_migration(xe, "requires gfx version >= 20, but only %u found",
+	if (GRAPHICS_VER(xe) < 12)
+		return vf_disable_migration(xe, "requires gfx version >= 12, but only %u found",
 					    GRAPHICS_VER(xe));
 
+	if (!xe_device_has_memirq(xe))
+		return vf_disable_migration(xe, "requires memory-based IRQ support");
+
 	xe->sriov.vf.migration.enabled = true;
 	xe_sriov_dbg(xe, "migration support enabled\n");
 }
-- 
2.25.1


  parent reply	other threads:[~2025-10-15  0:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15  0:27 [PATCH v2 0/4] drm/xe/vf: Minor fixes to post-migration recovery Tomasz Lis
2025-10-15  0:27 ` [PATCH v2 1/4] drm/xe/vf: Fix GuC FW check for VF migration support Tomasz Lis
2025-10-16  2:58   ` Matthew Brost
2025-10-15  0:27 ` [PATCH v2 2/4] drm/xe/vf: Skip fixups on VF migration before getting GGTT info Tomasz Lis
2025-10-15  0:27 ` [PATCH v2 3/4] drm/xe: Assert that VF will never use fixed placement of BOs Tomasz Lis
2025-10-15  0:27 ` Tomasz Lis [this message]
2025-10-15  0:33 ` ✓ CI.KUnit: success for drm/xe/vf: Minor fixes to post-migration recovery (rev2) Patchwork
2025-10-15  1:13 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-15 13:02 ` ✗ 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=20251015002755.720992-5-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