Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	"José Roberto de Souza" <jose.souza@intel.com>
Subject: Re: [PATCH] drm/xe: Mark reserved engines in snapshot
Date: Fri, 6 Sep 2024 21:07:19 +0000	[thread overview]
Message-ID: <ZttvB/xfNUwYVlp6@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240906205609.3131330-1-lucas.demarchi@intel.com>

On Fri, Sep 06, 2024 at 01:56:09PM -0700, Lucas De Marchi wrote:
> When printing <debufs>/gt*/hw_engines, it's useful to mark
> what engines are reserved so it doesn't mislead developers
> while debugging.
> 
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>

Seems useful. With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_hw_engine.c       | 3 +++
>  drivers/gpu/drm/xe/xe_hw_engine_types.h | 2 ++
>  2 files changed, 5 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c b/drivers/gpu/drm/xe/xe_hw_engine.c
> index c9c3beb3ce8d..ce180faf2592 100644
> --- a/drivers/gpu/drm/xe/xe_hw_engine.c
> +++ b/drivers/gpu/drm/xe/xe_hw_engine.c
> @@ -903,6 +903,7 @@ xe_hw_engine_snapshot_capture(struct xe_hw_engine *hwe)
>  	snapshot->forcewake.ref = xe_force_wake_ref(gt_to_fw(hwe->gt),
>  						    hwe->domain);
>  	snapshot->mmio_base = hwe->mmio_base;
> +	snapshot->kernel_reserved = xe_hw_engine_is_reserved(hwe);
>  
>  	/* no more VF accessible data below this point */
>  	if (IS_SRIOV_VF(gt_to_xe(hwe->gt)))
> @@ -1025,6 +1026,8 @@ void xe_hw_engine_snapshot_print(struct xe_hw_engine_snapshot *snapshot,
>  		   snapshot->logical_instance);
>  	drm_printf(p, "\tForcewake: domain 0x%x, ref %d\n",
>  		   snapshot->forcewake.domain, snapshot->forcewake.ref);
> +	drm_printf(p, "\tReserved: %s\n",
> +		   str_yes_no(snapshot->kernel_reserved));
>  	drm_printf(p, "\tHWSTAM: 0x%08x\n", snapshot->reg.ring_hwstam);
>  	drm_printf(p, "\tRING_HWS_PGA: 0x%08x\n", snapshot->reg.ring_hws_pga);
>  	drm_printf(p, "\tRING_EXECLIST_STATUS: 0x%016llx\n",
> diff --git a/drivers/gpu/drm/xe/xe_hw_engine_types.h b/drivers/gpu/drm/xe/xe_hw_engine_types.h
> index 8be6d420ece4..be60edb3e673 100644
> --- a/drivers/gpu/drm/xe/xe_hw_engine_types.h
> +++ b/drivers/gpu/drm/xe/xe_hw_engine_types.h
> @@ -173,6 +173,8 @@ struct xe_hw_engine_snapshot {
>  	} forcewake;
>  	/** @mmio_base: MMIO base address of this hw engine*/
>  	u32 mmio_base;
> +	/** @kernel_reserved: Engine reserved, can't be used by userspace */
> +	bool kernel_reserved;
>  	/** @reg: Useful MMIO register snapshot */
>  	struct {
>  		/** @reg.ring_execlist_status: RING_EXECLIST_STATUS */
> -- 
> 2.43.0
> 

  reply	other threads:[~2024-09-06 21:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 20:56 [PATCH] drm/xe: Mark reserved engines in snapshot Lucas De Marchi
2024-09-06 21:07 ` Matthew Brost [this message]
2024-09-06 21:08 ` Souza, Jose
2024-09-06 21:49 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-06 21:49 ` ✓ CI.checkpatch: " Patchwork
2024-09-06 21:50 ` ✓ CI.KUnit: " Patchwork
2024-09-06 22:02 ` ✓ CI.Build: " Patchwork
2024-09-06 22:05 ` ✓ CI.Hooks: " Patchwork
2024-09-06 22:06 ` ✓ CI.checksparse: " Patchwork
2024-09-06 22:48 ` ✓ CI.BAT: " Patchwork
2024-09-09 14:12 ` ✓ CI.FULL: " Patchwork
2024-09-09 18:06 ` [PATCH] " Lucas De Marchi

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=ZttvB/xfNUwYVlp6@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@intel.com \
    --cc=lucas.demarchi@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