From: Matthew Brost <matthew.brost@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/gt_pagefault: Print engine class string
Date: Wed, 29 Jan 2025 10:14:29 -0800 [thread overview]
Message-ID: <Z5pwBX4feHBFBYkW@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <20250129175241.338043-1-francois.dugast@intel.com>
On Wed, Jan 29, 2025 at 06:52:41PM +0100, Francois Dugast wrote:
> The engine class index which is printed here is an internal representation
> for debugging. It is _not_ an index based on DRM_XE_ENGINE_CLASS_* values
> provided in the uAPI. Add the string representation of the engine class to
> the output in order to limit possible confusion by users when analyzing the
> logs.
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_pagefault.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_pagefault.c b/drivers/gpu/drm/xe/xe_gt_pagefault.c
> index 2606cd396df5..cb92fb5cbc75 100644
> --- a/drivers/gpu/drm/xe/xe_gt_pagefault.c
> +++ b/drivers/gpu/drm/xe/xe_gt_pagefault.c
> @@ -263,12 +263,13 @@ static void print_pagefault(struct xe_device *xe, struct pagefault *pf)
> "\tFaultType: %d\n"
> "\tAccessType: %d\n"
> "\tFaultLevel: %d\n"
> - "\tEngineClass: %d\n"
> + "\tEngineClass: %d %s\n"
> "\tEngineInstance: %d\n",
> pf->asid, pf->vfid, pf->pdata, upper_32_bits(pf->page_addr),
> lower_32_bits(pf->page_addr),
> pf->fault_type, pf->access_type, pf->fault_level,
> - pf->engine_class, pf->engine_instance);
> + pf->engine_class, xe_hw_engine_class_to_str(pf->engine_class),
> + pf->engine_instance);
> }
>
> #define PF_MSG_LEN_DW 4
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-01-29 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 17:52 [PATCH] drm/xe/gt_pagefault: Print engine class string Francois Dugast
2025-01-29 18:14 ` Matthew Brost [this message]
2025-01-29 20:00 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-29 20:00 ` ✓ CI.checkpatch: " Patchwork
2025-01-29 20:02 ` ✓ CI.KUnit: " Patchwork
2025-01-29 20:25 ` ✓ CI.Build: " Patchwork
2025-01-29 20:27 ` ✓ CI.Hooks: " Patchwork
2025-01-29 20:29 ` ✓ CI.checksparse: " Patchwork
2025-01-29 20:51 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-30 3:00 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-30 8:21 ` Patchwork
2025-01-31 7:48 ` 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=Z5pwBX4feHBFBYkW@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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