Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Ilia Levi <illevi@habana.ai>, intel-xe@lists.freedesktop.org
Cc: ilia.levi@intel.com, jonathan.cavitt@intel.com,
	koby.elbaz@intel.com, yaron.avizrat@intel.com
Subject: Re: [PATCH v5 1/5] drm/xe: Introduce dedicated config for memirq debug
Date: Tue, 17 Sep 2024 22:07:56 +0200	[thread overview]
Message-ID: <9f9a1f77-4a36-4ee7-8cf3-4c3ec7a4b32b@intel.com> (raw)
In-Reply-To: <20240917112307.1242329-2-illevi@habana.ai>



On 17.09.2024 13:23, Ilia Levi wrote:
> From: Ilia Levi <ilia.levi@intel.com>
> 
> Separate config for memory based interrupts (memirq) infrastructure.

s/for/for debugging

> 
> Signed-off-by: Ilia Levi <ilia.levi@intel.com>
> ---
>  drivers/gpu/drm/xe/Kconfig.debug | 12 ++++++++++++

maybe I wasn't clear but in addition to Kconfig change I was expecting
those small adjustments in memirq_debug() macro definition to be
included in this patch:

-#define memirq_debug(m, msg...)	xe_sriov_dbg_verbose(...)
+
+#define memirq_printk(m, _level, _fmt, ...)			\
+	drm_##_level(&memirq_to_xe(m)->drm, "MEMIRQ%u: " _fmt,	\
+		     memirq_to_tile(m)->id, ##__VA_ARGS__)
+
+#ifdef CONFIG_DRM_XE_DEBUG_MEMIRQ
+#define memirq_debug(m, _fmt, ...)	memirq_printk(m, dbg, _fmt,
##__VA_ARGS__)
+#else
+#define memirq_debug(...)
+#endif
+

>  1 file changed, 12 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/Kconfig.debug b/drivers/gpu/drm/xe/Kconfig.debug
> index bc177368af6c..2de0de41b8dd 100644
> --- a/drivers/gpu/drm/xe/Kconfig.debug
> +++ b/drivers/gpu/drm/xe/Kconfig.debug
> @@ -40,9 +40,21 @@ config DRM_XE_DEBUG_VM
>  
>  	  If in doubt, say "N".
>  
> +config DRM_XE_DEBUG_MEMIRQ
> +	bool "Enable extra memirq debugging"
> +	default n
> +	help
> +	  Choose this option to enable additional debugging info for
> +	  memory based interrupts.
> +
> +	  Recommended for driver developers only.
> +
> +	  If in doubt, say "N".
> +
>  config DRM_XE_DEBUG_SRIOV
>  	bool "Enable extra SR-IOV debugging"
>  	default n
> +	select DRM_XE_DEBUG_MEMIRQ
>  	help
>  	  Enable extra SR-IOV debugging info.
>  

  reply	other threads:[~2024-09-17 20:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17 11:23 [PATCH v5 0/5] memirq infra changes Ilia Levi
2024-09-17 11:23 ` [PATCH v5 1/5] drm/xe: Introduce dedicated config for memirq debug Ilia Levi
2024-09-17 20:07   ` Michal Wajdeczko [this message]
2024-09-17 11:23 ` [PATCH v5 2/5] drm/xe: Introduce xe_device_uses_memirq() Ilia Levi
2024-09-17 19:16   ` Michal Wajdeczko
2024-09-17 11:23 ` [PATCH v5 3/5] drm/xe: move memirq out of VF Ilia Levi
2024-09-17 20:14   ` Michal Wajdeczko
2024-09-17 11:23 ` [PATCH v5 4/5] drm/xe: memirq infra changes for MSI-X Ilia Levi
2024-09-17 19:29   ` Michal Wajdeczko
2024-09-17 11:23 ` [PATCH v5 5/5] drm/xe: memirq handler changes Ilia Levi
2024-09-17 19:53   ` Michal Wajdeczko
2024-09-17 11:41 ` ✓ CI.Patch_applied: success for memirq infra changes (rev6) Patchwork
2024-09-17 11:42 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-17 11:43 ` ✓ CI.KUnit: success " Patchwork
2024-09-17 11:55 ` ✓ CI.Build: " Patchwork
2024-09-17 11:57 ` ✓ CI.Hooks: " Patchwork
2024-09-17 11:58 ` ✓ CI.checksparse: " Patchwork
2024-09-17 13:13 ` ✗ CI.BAT: failure " Patchwork
2024-09-17 15:16 ` ✗ CI.FULL: " 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=9f9a1f77-4a36-4ee7-8cf3-4c3ec7a4b32b@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=ilia.levi@intel.com \
    --cc=illevi@habana.ai \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=koby.elbaz@intel.com \
    --cc=yaron.avizrat@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