Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/xe/vf: Rename sriov_update_device_info
Date: Mon, 29 Sep 2025 09:46:50 +0200	[thread overview]
Message-ID: <20250929074650.bslznnd2g5hn3p7g@intel.com> (raw)
In-Reply-To: <20250928174811.198933-2-michal.wajdeczko@intel.com>

Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on nie [2025-wrz-28 19:48:10 +0200]:
> This is a VF only function and its name should reflect that to
> avoid any confusion. Move the VF check to the caller side.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_device.c | 18 +++++++++---------
>  1 file changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 09f8a66c9728..0421042597a2 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -688,16 +688,15 @@ static int wait_for_lmem_ready(struct xe_device *xe)
>  }
>  ALLOW_ERROR_INJECTION(wait_for_lmem_ready, ERRNO); /* See xe_pci_probe() */
>  
> -static void sriov_update_device_info(struct xe_device *xe)
> +static void vf_update_device_info(struct xe_device *xe)
>  {
> +	xe_assert(xe, IS_SRIOV_VF(xe));
>  	/* disable features that are not available/applicable to VFs */
> -	if (IS_SRIOV_VF(xe)) {
> -		xe->info.probe_display = 0;
> -		xe->info.has_heci_cscfi = 0;
> -		xe->info.has_heci_gscfi = 0;
> -		xe->info.skip_guc_pc = 1;
> -		xe->info.skip_pcode = 1;
> -	}
> +	xe->info.probe_display = 0;
> +	xe->info.has_heci_cscfi = 0;
> +	xe->info.has_heci_gscfi = 0;
> +	xe->info.skip_guc_pc = 1;
> +	xe->info.skip_pcode = 1;
>  }
>  
>  static int xe_device_vram_alloc(struct xe_device *xe)
> @@ -738,7 +737,8 @@ int xe_device_probe_early(struct xe_device *xe)
>  
>  	xe_sriov_probe_early(xe);
>  
> -	sriov_update_device_info(xe);
> +	if (IS_SRIOV_VF(xe))
> +		vf_update_device_info(xe);
>  
>  	err = xe_pcode_probe_early(xe);
>  	if (err || xe_survivability_mode_is_requested(xe)) {

LGTM:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>

> -- 
> 2.47.1
> 

-- 

  reply	other threads:[~2025-09-29  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 17:48 [PATCH 0/2] Don't claim support for firmware late-bind if VF Michal Wajdeczko
2025-09-28 17:48 ` [PATCH 1/2] drm/xe/vf: Rename sriov_update_device_info Michal Wajdeczko
2025-09-29  7:46   ` Piotr Piórkowski [this message]
2025-09-28 17:48 ` [PATCH 2/2] drm/xe/vf: Don't claim support for firmware late-bind if VF Michal Wajdeczko
2025-09-29  8:01   ` Piotr Piórkowski
2025-09-29  8:55   ` Nilawar, Badal
2025-09-28 17:55 ` ✓ CI.KUnit: success for " Patchwork
2025-09-28 18:32 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-28 19:52 ` ✓ 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=20250929074650.bslznnd2g5hn3p7g@intel.com \
    --to=piotr.piorkowski@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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