Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Don't force DRM_XE_DEBUG_MEMIRQ for SR-IOV debug
Date: Mon, 6 Oct 2025 15:42:25 +0200	[thread overview]
Message-ID: <20251006134225.oktwpyr4sisidmk5@intel.com> (raw)
In-Reply-To: <20251002171308.203127-1-michal.wajdeczko@intel.com>

Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on czw [2025-paź-02 19:13:08 +0200]:
> For pure SR-IOV debugging there is no need to select already
> separated config for the debugging of the memory based interrupts,
> as the latter is also very noisy on its own. Change config order
> and use a weak reverse dependency instead.
> 
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/Kconfig.debug | 22 +++++++++++-----------
>  1 file changed, 11 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/Kconfig.debug b/drivers/gpu/drm/xe/Kconfig.debug
> index 87902b4bd6d3..01227c77f6d7 100644
> --- a/drivers/gpu/drm/xe/Kconfig.debug
> +++ b/drivers/gpu/drm/xe/Kconfig.debug
> @@ -40,6 +40,17 @@ config DRM_XE_DEBUG_VM
>  
>  	  If in doubt, say "N".
>  
> +config DRM_XE_DEBUG_SRIOV
> +	bool "Enable extra SR-IOV debugging"
> +	default n
> +	imply DRM_XE_DEBUG_MEMIRQ
> +	help
> +	  Enable extra SR-IOV debugging info.
> +
> +	  Recommended for driver developers only.
> +
> +	  If in doubt, say "N".
> +
>  config DRM_XE_DEBUG_MEMIRQ
>  	bool "Enable extra memirq debugging"
>  	default n
> @@ -51,17 +62,6 @@ config DRM_XE_DEBUG_MEMIRQ
>  
>  	  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.
> -
> -	  Recommended for driver developers only.
> -
> -	  If in doubt, say "N".
> -
>  config DRM_XE_DEBUG_MEM
>  	bool "Enable passing SYS/VRAM addresses to user space"
>  	default n

LGTM:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> -- 
> 2.47.1
> 

-- 

      parent reply	other threads:[~2025-10-06 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-02 17:13 [PATCH] drm/xe: Don't force DRM_XE_DEBUG_MEMIRQ for SR-IOV debug Michal Wajdeczko
2025-10-02 17:33 ` Cavitt, Jonathan
2025-10-02 17:36 ` ✗ CI.checkpatch: warning for " Patchwork
2025-10-02 17:37 ` ✓ CI.KUnit: success " Patchwork
2025-10-02 18:13 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-02 20:46 ` ✓ Xe.CI.Full: " Patchwork
2025-10-06 13:42 ` Piotr Piórkowski [this message]

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=20251006134225.oktwpyr4sisidmk5@intel.com \
    --to=piotr.piorkowski@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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