Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: Re: [PATCH] drm/xe/xe3p_xpc: Add new XeCore fuse registers to VF runtime regs
Date: Thu, 12 Feb 2026 10:35:55 -0800	[thread overview]
Message-ID: <cf5e06e4-39e2-4b49-afed-4964a639ba6f@linux.intel.com> (raw)
In-Reply-To: <20260210182519.206952-2-matthew.d.roper@intel.com>

Hi Matt,

On 2026-02-10 10:25, Matt Roper wrote:
> SRIOV VFs do not automatically have access to the XeCore fuse registers.
> Add the two new registers that show up on Xe3p_XPC to the runtime
> register list to grant VFs access.  Since there's a single runtime
> register list for all Xe3p, this will technically also grant access on
> Xe3p_LPG platforms where the registers don't exist, but that should be
> harmless since even if a VF tries to read a non-existent register on
> those platforms it will just get back a sensible value of 0x0.
>
> Fixes: e8100643ff01 ("drm/xe/xe3p_xpc: XeCore mask spans four registers")
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
This looks good to me.

Reviewed-by: Ngai-Mint Kwan <ngai-mint.kwan@linux.intel.com>

Thanks,
Ngai-Mint Kwan
> ---
>   drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
> index b5e0a5b7723e..6586df2fcb91 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_service.c
> @@ -111,6 +111,8 @@ static const struct xe_reg ver_35_runtime_regs[] = {
>   	XE2_GT_COMPUTE_DSS_2,		/* _MMIO(0x914c) */
>   	XE2_GT_GEOMETRY_DSS_1,		/* _MMIO(0x9150) */
>   	XE2_GT_GEOMETRY_DSS_2,		/* _MMIO(0x9154) */
> +	XE3P_XPC_GT_GEOMETRY_DSS_3,	/* _MMIO(0x915c) */
> +	XE3P_XPC_GT_COMPUTE_DSS_3,	/* _MMIO(0x9160) */
>   	SERVICE_COPY_ENABLE,		/* _MMIO(0x9170) */
>   };
>   


      parent reply	other threads:[~2026-02-12 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 18:25 [PATCH] drm/xe/xe3p_xpc: Add new XeCore fuse registers to VF runtime regs Matt Roper
2026-02-10 18:31 ` ✓ CI.KUnit: success for " Patchwork
2026-02-10 19:06 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-11  1:33 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-12 19:04   ` Matt Roper
2026-02-12 18:35 ` Ngai-Mint Kwan [this message]

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=cf5e06e4-39e2-4b49-afed-4964a639ba6f@linux.intel.com \
    --to=ngai-mint.kwan@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --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