From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Matthew Brost <matthew.brost@intel.com>,
Tomasz Lis <tomasz.lis@intel.com>
Subject: Re: [PATCH v5 1/3] drm/xe/vf: Enable VF migration only on supported GuC versions
Date: Thu, 20 Nov 2025 22:18:14 +0100 [thread overview]
Message-ID: <ee33f64c-052f-473a-a8f9-08d597dce87c@intel.com> (raw)
In-Reply-To: <20251120145157.6995-6-satyanarayana.k.v.p@intel.com>
On 11/20/2025 3:51 PM, Satyanarayana K V P wrote:
> Enable VF migration starting with GuC 70.54.0 (compatibility version
> 1.27.0).
this is only says "what", for the "why" part we likely want to add:
" ... which supports additional VF2GUC_RESFIX_START message required
to handle migration recovery in a more robust way."
>
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Tomasz Lis <tomasz.lis@intel.com>
>
> ---
> V4 -> V5:
> - Created new function vf_migration_init_late() (Michal W).
>
> V3 -> V4:
> - New commit
>
> V2 -> V3:
> - None.
>
> V1 -> V2:
> - None.
> ---
> drivers/gpu/drm/xe/xe_sriov_vf.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf.c b/drivers/gpu/drm/xe/xe_sriov_vf.c
> index 284ce37ca92d..13cacdbbf2d2 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_vf.c
> +++ b/drivers/gpu/drm/xe/xe_sriov_vf.c
> @@ -170,6 +170,20 @@ void xe_sriov_vf_init_early(struct xe_device *xe)
> vf_migration_init_early(xe);
> }
>
> +static void vf_migration_init_late(struct xe_device *xe)
> +{
> + struct xe_gt *gt = xe_root_mmio_gt(xe);
> + struct xe_uc_fw_version guc_version;
maybe we should call xe_sriov_vf_migration_supported() too?
> +
> + xe_gt_sriov_vf_guc_versions(gt, NULL, &guc_version);
> + if (MAKE_GUC_VER_STRUCT(guc_version) < MAKE_GUC_VER(1, 27, 0)) {
> + xe_sriov_vf_migration_disable(xe,
> + "requires GUC ABI >= 1.27.0, but only %u.%u.%u found",
s/GUC/GuC
> + guc_version.major, guc_version.minor,
> + guc_version.patch);
> + }
and return bool/true only if we still claim support for migration?
> +}
> +
> /**
> * xe_sriov_vf_init_late() - SR-IOV VF late initialization functions.
> * @xe: the &xe_device to initialize
> @@ -180,6 +194,7 @@ void xe_sriov_vf_init_early(struct xe_device *xe)
> */
> int xe_sriov_vf_init_late(struct xe_device *xe)
> {
> + vf_migration_init_late(xe);
then here we can have:
if (!vf_migration_init_late(xe))
return 0;
> return xe_sriov_vf_ccs_init(xe);
> }
>
next prev parent reply other threads:[~2025-11-20 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 14:51 [PATCH v5 0/3] VF double migration Satyanarayana K V P
2025-11-20 14:51 ` [PATCH v5 1/3] drm/xe/vf: Enable VF migration only on supported GuC versions Satyanarayana K V P
2025-11-20 21:18 ` Michal Wajdeczko [this message]
2025-11-20 14:52 ` [PATCH v5 2/3] drm/xe/vf: Introduce RESFIX start marker support Satyanarayana K V P
2025-11-20 21:37 ` Michal Wajdeczko
2025-11-20 14:52 ` [PATCH v5 3/3] drm/xe/vf: Add debugfs entries to test VF double migration Satyanarayana K V P
2025-11-20 21:53 ` Michal Wajdeczko
2025-11-21 7:21 ` Matthew Brost
2025-11-20 16:01 ` ✓ CI.KUnit: success for VF double migration (rev5) Patchwork
2025-11-20 16:40 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-20 21:10 ` ✗ 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=ee33f64c-052f-473a-a8f9-08d597dce87c@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=satyanarayana.k.v.p@intel.com \
--cc=tomasz.lis@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;
as well as URLs for NNTP newsgroup(s).