Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v4 1/3] drm/xe/vf: Enable VF migration only on supported GUC versions
Date: Wed, 19 Nov 2025 15:47:12 +0100	[thread overview]
Message-ID: <852d2d8e-e54b-40ed-84d1-23e6bd8a3a5d@intel.com> (raw)
In-Reply-To: <20251118114116.3429730-2-satyanarayana.k.v.p@intel.com>



On 11/18/2025 12:41 PM, Satyanarayana K V P wrote:
> Enable VF migration starting with GUC 70.54.0 (compatibility version
> 1.27.0). Gate the feature on the GuC firmware version and keep it disabled
> on older or unsupported versions.

hmm, do we need this second sentence?

and please use "GuC" naming everywhere

> 
> 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>
> 
> ---
> V3 -> V4:
> - New commit
> 
> V2 -> V3:
> - None.
> 
> V1 -> V2:
> - None.
> ---
>  drivers/gpu/drm/xe/xe_sriov_vf.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf.c b/drivers/gpu/drm/xe/xe_sriov_vf.c
> index 284ce37ca92d..b73498097df5 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_vf.c
> +++ b/drivers/gpu/drm/xe/xe_sriov_vf.c
> @@ -180,6 +180,18 @@ void xe_sriov_vf_init_early(struct xe_device *xe)
>   */
>  int xe_sriov_vf_init_late(struct xe_device *xe)
>  {
> +	struct xe_gt *gt = xe_root_mmio_gt(xe);
> +	struct xe_uc_fw_version guc_version;
> +
> +	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",
> +					      guc_version.major, guc_version.minor,
> +					      guc_version.patch);
> +		return 0;
> +	}

and move this code to the vf_migration_init_late() helper, like
we did in xe_sriov_vf_init_early() and vf_migration_init_early()

> +
>  	return xe_sriov_vf_ccs_init(xe);
>  }
>  


  reply	other threads:[~2025-11-19 14:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 11:41 [PATCH v4 0/3] VF double migration Satyanarayana K V P
2025-11-18 11:41 ` [PATCH v4 1/3] drm/xe/vf: Enable VF migration only on supported GUC versions Satyanarayana K V P
2025-11-19 14:47   ` Michal Wajdeczko [this message]
2025-11-18 11:41 ` [PATCH v4 2/3] drm/xe/vf: Introduce RESFIX start marker support Satyanarayana K V P
2025-11-19 17:24   ` Michal Wajdeczko
2025-11-19 17:38     ` Matthew Brost
2025-11-20 13:33       ` K V P, Satyanarayana
2025-11-18 11:41 ` [PATCH v4 3/3] drm/xe/vf: Add debugfs entries to test VF double migration Satyanarayana K V P
2025-11-19 17:51   ` Michal Wajdeczko
2025-11-20 13:35     ` K V P, Satyanarayana
2025-11-18 12:31 ` ✓ CI.KUnit: success for VF double migration (rev4) Patchwork
2025-11-18 13:09 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-18 15:19 ` ✗ 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=852d2d8e-e54b-40ed-84d1-23e6bd8a3a5d@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