Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 2/4] drm/xe/vf: Boostrap all GTs immediately after MMIO init
Date: Thu, 29 May 2025 22:49:07 +0200	[thread overview]
Message-ID: <65eaaf43-a80b-4e96-bc96-a0e48d416dcf@intel.com> (raw)
In-Reply-To: <20250528234229.4185039-8-daniele.ceraolospurio@intel.com>



On 29.05.2025 01:42, Daniele Ceraolo Spurio wrote:
> Currently we perform the bootstrap for the primary GT early on during
> device init, while the media GT bootstrap happens when we try and fetch
> the hwconfig table. For consistency, move the bootstrap of the media GT
> happen at the same time as the primary GT, so that all the subsequent
> code can rely on both GTs being in the same state.
> 
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_device.c | 11 ++++++-----
>  drivers/gpu/drm/xe/xe_guc.c    |  4 ----
>  2 files changed, 6 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 660b0c5126dc..7e87344943cd 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -798,18 +798,19 @@ int xe_device_probe(struct xe_device *xe)
>  		 * be performed.
>  		 */
>  		xe_gt_mmio_init(gt);
> -	}
>  
> -	for_each_tile(tile, xe, id) {
>  		if (IS_SRIOV_VF(xe)) {
> -			xe_guc_comm_init_early(&tile->primary_gt->uc.guc);
> -			err = xe_gt_sriov_vf_bootstrap(tile->primary_gt);
> +			xe_guc_comm_init_early(&gt->uc.guc);
> +			err = xe_gt_sriov_vf_bootstrap(gt);
>  			if (err)
>  				return err;
> -			err = xe_gt_sriov_vf_query_config(tile->primary_gt);
> +			err = xe_gt_sriov_vf_query_config(gt);
>  			if (err)
>  				return err;
>  		}
> +	}
> +
> +	for_each_tile(tile, xe, id) {
>  		err = xe_ggtt_init_early(tile->mem.ggtt);
>  		if (err)
>  			return err;
> diff --git a/drivers/gpu/drm/xe/xe_guc.c b/drivers/gpu/drm/xe/xe_guc.c
> index 350434a8b953..065550964e68 100644
> --- a/drivers/gpu/drm/xe/xe_guc.c
> +++ b/drivers/gpu/drm/xe/xe_guc.c
> @@ -1102,10 +1102,6 @@ static int vf_guc_min_load_for_hwconfig(struct xe_guc *guc)
>  	struct xe_gt *gt = guc_to_gt(guc);
>  	int ret;
>  
> -	ret = xe_gt_sriov_vf_bootstrap(gt);
> -	if (ret)
> -		return ret;
> -
>  	ret = xe_gt_sriov_vf_query_config(gt);

we likely don't need this either as config was read in xe_device_probe()

otherwise LGTM

>  	if (ret)
>  		return ret;


  reply	other threads:[~2025-05-29 20:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 23:42 [PATCH v2 0/4] Fixes for VF GuC version Daniele Ceraolo Spurio
2025-05-28 23:42 ` [PATCH v2 1/4] drm/xe/uc: Prepare uc_fw_version for storing the VF ABI version Daniele Ceraolo Spurio
2025-05-29 20:35   ` Michal Wajdeczko
2025-05-28 23:42 ` [PATCH v2 2/4] drm/xe/vf: Boostrap all GTs immediately after MMIO init Daniele Ceraolo Spurio
2025-05-29 20:49   ` Michal Wajdeczko [this message]
2025-05-28 23:42 ` [PATCH v2 3/4] drm/xe/vf: Use uc_fw_version to store the negotiated GuC ABI Daniele Ceraolo Spurio
2025-05-28 23:42 ` [PATCH v2 4/4] drm/xe/vf: Store the GuC FW info in guc->fw Daniele Ceraolo Spurio
2025-05-30 13:55   ` Michal Wajdeczko
2025-05-28 23:48 ` ✓ CI.Patch_applied: success for Fixes for VF GuC version Patchwork
2025-05-28 23:48 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-28 23:50 ` ✓ CI.KUnit: success " Patchwork
2025-05-29  0:00 ` ✓ CI.Build: " Patchwork
2025-05-29  0:03 ` ✓ CI.Hooks: " Patchwork
2025-05-29  0:04 ` ✓ CI.checksparse: " Patchwork
2025-05-29  0:49 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-29  6:21 ` ✓ 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=65eaaf43-a80b-4e96-bc96-a0e48d416dcf@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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