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 v2 1/9] drm/xe/vf: Disable features that do not apply to VFs
Date: Thu, 20 Jun 2024 12:06:39 +0200	[thread overview]
Message-ID: <20240620100639.cnl3jnc2np6wvcy3@intel.com> (raw)
In-Reply-To: <20240620100147.949-1-michal.wajdeczko@intel.com>

Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on czw [2024-cze-20 12:01:47 +0200]:
> We already maintain several flags that control the availability
> of features on a given device. Disable features, like PCODE or
> GuC PC or GSC, that do not apply to a VF device.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Piotr Piórkowski <piotr.piorkowski@intel.com>
> ---
> v2: also disable display (Piotr)
> ---
>  drivers/gpu/drm/xe/xe_device.c | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 75d4c8ae9234..0d57eea8f083 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -486,6 +486,17 @@ static int wait_for_lmem_ready(struct xe_device *xe)
>  	return 0;
>  }
>  
> +static void update_device_info(struct xe_device *xe)
> +{
> +	/* disable features that are not available/applicable to VFs */
> +	if (IS_SRIOV_VF(xe)) {
> +		xe->info.enable_display = 0;
> +		xe->info.has_heci_gscfi = 0;
> +		xe->info.skip_guc_pc = 1;
> +		xe->info.skip_pcode = 1;
> +	}
> +}
> +
>  /**
>   * xe_device_probe_early: Device early probe
>   * @xe: xe device instance
> @@ -506,6 +517,8 @@ int xe_device_probe_early(struct xe_device *xe)
>  
>  	xe_sriov_probe_early(xe);
>  
> +	update_device_info(xe);
> +
>  	err = xe_pcode_probe_early(xe);
>  	if (err)
>  		return err;

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

-- 

  reply	other threads:[~2024-06-20 10:06 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 21:45 [PATCH 0/9] Adapt the driver to boot on the VF device Michal Wajdeczko
2024-06-19 21:45 ` [PATCH 1/9] drm/xe/vf: Disable features that do not apply to VFs Michal Wajdeczko
2024-06-20  9:17   ` Piotr Piórkowski
2024-06-20 10:05     ` Michal Wajdeczko
2024-06-20 10:01   ` [PATCH v2 " Michal Wajdeczko
2024-06-20 10:06     ` Piotr Piórkowski [this message]
2024-06-19 21:45 ` [PATCH 2/9] drm/xe/vf: Don't run any save-restore RTP actions if VF Michal Wajdeczko
2024-06-20  9:20   ` Piotr Piórkowski
2024-06-20 17:30   ` Matt Roper
2024-06-19 21:45 ` [PATCH 3/9] drm/xe/vf: Don't apply tile workarounds " Michal Wajdeczko
2024-06-20  9:21   ` Piotr Piórkowski
2024-06-20 17:31   ` Matt Roper
2024-06-19 21:45 ` [PATCH 4/9] drm/xe/vf: Don't change hwe IRQ masks if using memory IRQs Michal Wajdeczko
2024-06-20  9:29   ` Piotr Piórkowski
2024-06-19 21:45 ` [PATCH 5/9] drm/xe/vf: Don't initialize OA if VF Michal Wajdeczko
2024-06-19 21:56   ` Dixit, Ashutosh
2024-06-19 22:10     ` Dixit, Ashutosh
2024-06-19 22:40       ` Michal Wajdeczko
2024-06-19 22:57         ` Dixit, Ashutosh
2024-06-19 23:01           ` Michal Wajdeczko
2024-06-19 21:45 ` [PATCH 6/9] drm/xe/vf: Don't support gtidle " Michal Wajdeczko
2024-06-20  9:38   ` Piotr Piórkowski
2024-06-19 21:45 ` [PATCH 7/9] drm/xe/vf: Don't use register based TLB invalidation " Michal Wajdeczko
2024-06-19 23:13   ` Matthew Brost
2024-06-19 23:25     ` Michal Wajdeczko
2024-06-20 10:07   ` Piotr Piórkowski
2024-06-19 21:45 ` [PATCH 8/9] drm/xe/vf: Skip engine ring enabling " Michal Wajdeczko
2024-06-20 10:03   ` Piotr Piórkowski
2024-06-19 21:45 ` [PATCH 9/9] drm/xe/vf: Custom HuC initialization " Michal Wajdeczko
2024-06-19 23:11   ` Matthew Brost
2024-06-19 23:14     ` Michal Wajdeczko
2024-06-19 23:23       ` Matthew Brost
2024-06-19 23:34         ` Michal Wajdeczko
2024-06-20  1:59           ` Matthew Brost
2024-06-19 21:51 ` ✓ CI.Patch_applied: success for Adapt the driver to boot on the VF device Patchwork
2024-06-19 21:51 ` ✓ CI.checkpatch: " Patchwork
2024-06-19 21:52 ` ✓ CI.KUnit: " Patchwork
2024-06-19 22:04 ` ✓ CI.Build: " Patchwork
2024-06-19 22:06 ` ✗ CI.Hooks: failure " Patchwork
2024-06-19 22:07 ` ✓ CI.checksparse: success " Patchwork
2024-06-19 22:22 ` ✗ CI.BAT: failure " Patchwork
2024-06-20  6:28   ` Michal Wajdeczko
2024-06-20  6:16 ` ✗ CI.FULL: " Patchwork
2024-06-20  6:28 ` ✓ CI.Patch_applied: success for Adapt the driver to boot on the VF device (rev2) Patchwork
2024-06-20  6:28 ` ✓ CI.checkpatch: " Patchwork
2024-06-20  6:29 ` ✓ CI.KUnit: " Patchwork
2024-06-20  6:41 ` ✓ CI.Build: " Patchwork
2024-06-20  6:43 ` ✗ CI.Hooks: failure " Patchwork
2024-06-20  6:44 ` ✓ CI.checksparse: success " Patchwork
2024-06-20  7:01 ` ✓ CI.BAT: " Patchwork
2024-06-20  8:32 ` ✗ CI.FULL: failure " Patchwork
2024-06-20 10:09 ` ✓ CI.Patch_applied: success for Adapt the driver to boot on the VF device (rev3) Patchwork
2024-06-20 10:09 ` ✓ CI.checkpatch: " Patchwork
2024-06-20 10:10 ` ✓ CI.KUnit: " Patchwork
2024-06-20 10:22 ` ✓ CI.Build: " Patchwork
2024-06-20 10:24 ` ✗ CI.Hooks: failure " Patchwork
2024-06-20 10:26 ` ✓ CI.checksparse: success " Patchwork
2024-06-20 10:52 ` ✗ CI.BAT: failure " Patchwork
2024-06-20 14:29   ` Michal Wajdeczko
2024-06-20 13:01 ` ✗ CI.FULL: " Patchwork
2024-06-20 14:32   ` Michal Wajdeczko

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=20240620100639.cnl3jnc2np6wvcy3@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