Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Varun Gupta <varun.gupta@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	<himal.prasad.ghimiray@intel.com>, <matthew.brost@intel.com>
Subject: Re: [PATCH 1/2] drm/xe: Coalesce pagefault error handling
Date: Mon, 12 Jan 2026 10:17:19 -0800	[thread overview]
Message-ID: <20260112181719.GD458797@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20260112061755.1569635-5-varun.gupta@intel.com>

On Mon, Jan 12, 2026 at 11:47:57AM +0530, Varun Gupta wrote:
> The page fault is only ever printed on when the fault handling fails.
> Use a single dbg with the fault response status and its details.

This commit message here seems to be a copy of the one from
https://lore.kernel.org/all/20251107-pagefault-prefetch-v1-1-93291d619126@intel.com/
but doesn't match the code changes below.  It looks like the change
below just renames the xe_pagefault_print() function and adds an
additional (currently unused) err parameter.

Maybe you intended some of the changes from patch #2 (incrementing the
stats counters) to be included in this patch?  Either way, the commit
message needs to be updated.


Matt

> 
> Originally-by: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> Signed-off-by: Varun Gupta <varun.gupta@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_pagefault.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_pagefault.c b/drivers/gpu/drm/xe/xe_pagefault.c
> index 6bee53d6ffc3..34dac4280b9d 100644
> --- a/drivers/gpu/drm/xe/xe_pagefault.c
> +++ b/drivers/gpu/drm/xe/xe_pagefault.c
> @@ -221,7 +221,7 @@ static bool xe_pagefault_queue_pop(struct xe_pagefault_queue *pf_queue,
>  	return found_fault;
>  }
>  
> -static void xe_pagefault_print(struct xe_pagefault *pf)
> +static void xe_pagefault_error_account(struct xe_pagefault *pf, int err)
>  {
>  	xe_gt_info(pf->gt, "\n\tASID: %d\n"
>  		   "\tFaulted Address: 0x%08x%08x\n"
> @@ -259,7 +259,7 @@ static void xe_pagefault_queue_work(struct work_struct *w)
>  
>  		err = xe_pagefault_service(&pf);
>  		if (err) {
> -			xe_pagefault_print(&pf);
> +			xe_pagefault_error_account(&pf, err);
>  			xe_gt_info(pf.gt, "Fault response: Unsuccessful %pe\n",
>  				   ERR_PTR(err));
>  		}
> -- 
> 2.43.0
> 

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

  reply	other threads:[~2026-01-12 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  6:17 [PATCH 0/2] drm/xe: Add prefetch pagefault support for Xe3p Varun Gupta
2026-01-12  6:17 ` [PATCH 1/2] drm/xe: Coalesce pagefault error handling Varun Gupta
2026-01-12 18:17   ` Matt Roper [this message]
2026-01-12  6:17 ` [PATCH 2/2] drm/xe: Add prefetch fault support for Xe3p Varun Gupta
2026-01-12  6:24 ` ✗ CI.checkpatch: warning for drm/xe: Add prefetch pagefault " Patchwork
2026-01-12  6:25 ` ✓ CI.KUnit: success " Patchwork
2026-01-12  6:57 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-12  8:04 ` ✗ 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=20260112181719.GD458797@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=varun.gupta@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