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>,
	"Satyanarayana K V P" <satyanarayana.k.v.p@intel.com>
Subject: [PATCH v6 0/4] drm/xe/vf: Minor fixes to post-migration recovery
Date: Tue, 21 Oct 2025 20:12:46 +0200	[thread overview]
Message-ID: <20251021181250.1541639-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()

v4: Remove platform version check, discard early MIGRATED ignore patch,
 move and rename CCS BB check functions, switch target of "Fixes" tag

v5: limit scope of some functions, switched 'Fixes:' tag to a different
 commit

v6: removed writing false zeroed var, squashed two patches,
 added kerneldoc, moved location of some checks

Tomasz Lis (4):
  drm/xe/vf: Revert logic of vf.migration.enabled
  drm/xe/vf: Fix GuC FW check for VF migration support
  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_sriov_vf.c       | 39 +++++++--------------
 drivers/gpu/drm/xe/xe_sriov_vf.h       |  1 +
 drivers/gpu/drm/xe/xe_sriov_vf_ccs.c   | 48 ++++++++++++++++++++++++--
 drivers/gpu/drm/xe/xe_sriov_vf_types.h |  6 ++--
 5 files changed, 69 insertions(+), 31 deletions(-)

-- 
2.25.1


             reply	other threads:[~2025-10-21 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 18:12 Tomasz Lis [this message]
2025-10-21 18:12 ` [PATCH v6 1/4] drm/xe/vf: Revert logic of vf.migration.enabled Tomasz Lis
2025-10-21 18:13   ` Michal Wajdeczko
2025-10-21 18:12 ` [PATCH v6 2/4] drm/xe/vf: Fix GuC FW check for VF migration support Tomasz Lis
2025-10-21 18:39   ` Michal Wajdeczko
2025-10-21 22:39     ` Lis, Tomasz
2025-10-21 18:12 ` [PATCH v6 3/4] drm/xe: Assert that VF will never use fixed placement of BOs Tomasz Lis
2025-10-21 18:12 ` [PATCH v6 4/4] drm/xe/vf: Do not disable VF migration on ATS-M Tomasz Lis
2025-10-21 18:18 ` ✓ CI.KUnit: success for drm/xe/vf: Minor fixes to post-migration recovery (rev6) 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=20251021181250.1541639-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