Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francois Dugast <francois.dugast@intel.com>
To: Matthew Brost <matthew.brost@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] drm/xe: Avoid touching consumer fields in GuC pagefault ack
Date: Fri, 13 Feb 2026 14:57:33 +0100	[thread overview]
Message-ID: <aY8tzTYJkkBnS0Wi@fdugast-desk> (raw)
In-Reply-To: <20260212204227.2764054-3-matthew.brost@intel.com>

On Thu, Feb 12, 2026 at 12:42:27PM -0800, Matthew Brost wrote:
> The GuC pagefault acknowledgement code is designed to extract the fields
> needed for the acknowledgement from the producer-stored message so that
> the consumer fields can be overloaded to return additional information.
> The ASID is stored in the producer message; extract it from there to
> future‑proof this logic.
> 
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Francois Dugast <francois.dugast@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_guc_pagefault.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_guc_pagefault.c b/drivers/gpu/drm/xe/xe_guc_pagefault.c
> index 1166b0a5fa21..d48f6ed103bb 100644
> --- a/drivers/gpu/drm/xe/xe_guc_pagefault.c
> +++ b/drivers/gpu/drm/xe/xe_guc_pagefault.c
> @@ -17,6 +17,7 @@ static void guc_ack_fault(struct xe_pagefault *pf, int err)
>  	u32 pdata = FIELD_GET(PFD_PDATA_LO, pf->producer.msg[0]) |
>  		(FIELD_GET(PFD_PDATA_HI, pf->producer.msg[1]) <<
>  		 PFD_PDATA_HI_SHIFT);
> +	u32 asid = FIELD_GET(PFD_ASID, pf->producer.msg[1]);
>  	u32 action[] = {
>  		XE_GUC_ACTION_PAGE_FAULT_RES_DESC,
>  
> @@ -24,7 +25,7 @@ static void guc_ack_fault(struct xe_pagefault *pf, int err)
>  		FIELD_PREP(PFR_SUCCESS, !!err) |
>  		FIELD_PREP(PFR_REPLY, PFR_ACCESS) |
>  		FIELD_PREP(PFR_DESC_TYPE, FAULT_RESPONSE_DESC) |
> -		FIELD_PREP(PFR_ASID, pf->consumer.asid),
> +		FIELD_PREP(PFR_ASID, asid),
>  
>  		FIELD_PREP(PFR_VFID, vfid) |
>  		FIELD_PREP(PFR_ENG_INSTANCE, engine_instance) |
> -- 
> 2.34.1
> 

  reply	other threads:[~2026-02-13 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 20:42 [PATCH 0/2] Low hanging pagefault refactors Matthew Brost
2026-02-12 20:42 ` [PATCH 1/2] drm/xe: Pack fault type and level into a u8 Matthew Brost
2026-02-13 13:30   ` Francois Dugast
2026-02-12 20:42 ` [PATCH 2/2] drm/xe: Avoid touching consumer fields in GuC pagefault ack Matthew Brost
2026-02-13 13:57   ` Francois Dugast [this message]
2026-02-12 20:47 ` ✗ CI.checkpatch: warning for Low hanging pagefault refactors Patchwork
2026-02-12 20:48 ` ✓ CI.KUnit: success " Patchwork
2026-02-12 21:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-14  0:20 ` ✗ Xe.CI.FULL: failure " 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=aY8tzTYJkkBnS0Wi@fdugast-desk \
    --to=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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