Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 7/8] drm/xe/vf: Don't program PAT if VF
Date: Fri, 12 Jan 2024 16:56:34 -0800	[thread overview]
Message-ID: <20240113005634.GD45138@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20240112152649.849-8-michal.wajdeczko@intel.com>

On Fri, Jan 12, 2024 at 04:26:48PM +0100, Michal Wajdeczko wrote:
> PAT programming can only be done by the PF driver.
> Besides VF drivers don't have access to control registers.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>

Reviewed-by: Matt Roper <matthew.d.roper@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_pat.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pat.c b/drivers/gpu/drm/xe/xe_pat.c
> index 1ff6bc79e7d4..e148934d554b 100644
> --- a/drivers/gpu/drm/xe/xe_pat.c
> +++ b/drivers/gpu/drm/xe/xe_pat.c
> @@ -13,6 +13,7 @@
>  #include "xe_gt.h"
>  #include "xe_gt_mcr.h"
>  #include "xe_mmio.h"
> +#include "xe_sriov.h"
>  
>  #define _PAT_ATS				0x47fc
>  #define _PAT_INDEX(index)			_PICK_EVEN_2RANGES(index, 8, \
> @@ -433,6 +434,10 @@ void xe_pat_init_early(struct xe_device *xe)
>  		drm_err(&xe->drm, "Missing PAT table for platform with graphics version %d.%02d!\n",
>  			GRAPHICS_VER(xe), GRAPHICS_VERx100(xe) % 100);
>  	}
> +
> +	/* VFs can't program nor dump PAT settings */
> +	if (IS_SRIOV_VF(xe))
> +		xe->pat.ops = NULL;
>  }
>  
>  void xe_pat_init(struct xe_gt *gt)
> -- 
> 2.25.1
> 

-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation

  reply	other threads:[~2024-01-13  0:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:26 [PATCH 0/8] VF Tweaks Michal Wajdeczko
2024-01-12 15:26 ` [PATCH 1/8] drm/xe/vf: Assume fixed GSM size if VF Michal Wajdeczko
2024-01-13  1:13   ` Matt Roper
2024-01-12 15:26 ` [PATCH 2/8] drm/xe/vf: Don't try to capture engine data unavailable to VF Michal Wajdeczko
2024-01-12 21:15   ` Rodrigo Vivi
2024-01-12 15:26 ` [PATCH 3/8] drm/xe/vf: Don't program MOCS if VF Michal Wajdeczko
2024-01-13  0:54   ` Matt Roper
2024-01-12 15:26 ` [PATCH 4/8] drm/xe/vf: Don't initialize stolen memory manager " Michal Wajdeczko
2024-02-06 17:47   ` Matt Roper
2024-01-12 15:26 ` [PATCH 5/8] drm/xe/vf: Don't check if LMEM is initialized " Michal Wajdeczko
2024-01-13  4:37   ` Matt Roper
2024-01-12 15:26 ` [PATCH 6/8] drm/xe/vf: Don't enable hwmon " Michal Wajdeczko
2024-01-16 20:04   ` Nilawar, Badal
2024-01-12 15:26 ` [PATCH 7/8] drm/xe/vf: Don't program PAT " Michal Wajdeczko
2024-01-13  0:56   ` Matt Roper [this message]
2024-01-12 15:26 ` [PATCH 8/8] drm/xe/vf: Don't support MCR registers " Michal Wajdeczko
2024-01-13  1:11   ` Matt Roper
2024-01-12 15:30 ` ✓ CI.Patch_applied: success for VF Tweaks Patchwork
2024-01-12 15:30 ` ✓ CI.checkpatch: " Patchwork
2024-01-12 15:31 ` ✓ CI.KUnit: " Patchwork
2024-01-12 15:38 ` ✓ CI.Build: " Patchwork
2024-01-12 15:38 ` ✓ CI.Hooks: " Patchwork
2024-01-12 15:40 ` ✓ CI.checksparse: " Patchwork
2024-01-12 16:03 ` ✓ CI.BAT: " 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=20240113005634.GD45138@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@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