Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
	<intel-xe@lists.freedesktop.org>
Cc: Michal Mrozek <michal.mrozek@intel.com>
Subject: Re: [PATCH 2/2] drm/xe: Annotate default for guc_log_level param
Date: Thu, 12 Jun 2025 11:26:41 -0700	[thread overview]
Message-ID: <b18ef656-adf9-4880-8839-c3484fe6ee8b@intel.com> (raw)
In-Reply-To: <20250612-guc-log-level-v1-2-51f124a3be6d@intel.com>

On 6/12/2025 11:05 AM, Lucas De Marchi wrote:
> Reword the parameter description so it's clear what's the default and
> what are the verbose levels.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>

> ---
>   drivers/gpu/drm/xe/xe_module.c | 6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_module.c b/drivers/gpu/drm/xe/xe_module.c
> index 4809afa7ce3f9..3ca25bea5a15a 100644
> --- a/drivers/gpu/drm/xe/xe_module.c
> +++ b/drivers/gpu/drm/xe/xe_module.c
> @@ -43,7 +43,11 @@ module_param_named(vram_bar_size, xe_modparam.force_vram_bar_size, int, 0600);
>   MODULE_PARM_DESC(vram_bar_size, "Set the vram bar size (in MiB) - <0=disable-resize, 0=max-needed-size[default], >0=force-size");
>   
>   module_param_named(guc_log_level, xe_modparam.guc_log_level, int, 0600);
> -MODULE_PARM_DESC(guc_log_level, "GuC firmware logging level (0=disable, 1..5=enable with verbosity min..max)");
> +#if IS_ENABLED(CONFIG_DRM_XE_DEBUG)
> +MODULE_PARM_DESC(guc_log_level, "GuC firmware logging level (0=disable, 1=normal, 2..5=verbose-levels [default=3])");
> +#else
> +MODULE_PARM_DESC(guc_log_level, "GuC firmware logging level (0=disable, 1=normal, 2..5=verbose-levels [default=1])");
> +#endif
>   
>   module_param_named_unsafe(guc_firmware_path, xe_modparam.guc_firmware_path, charp, 0400);
>   MODULE_PARM_DESC(guc_firmware_path,
>


  reply	other threads:[~2025-06-12 18:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 18:05 [PATCH 0/2] drm/xe: Tweak default GuC log level Lucas De Marchi
2025-06-12 18:05 ` [PATCH 1/2] drm/xe/guc: Default log level to non-verbose Lucas De Marchi
2025-06-12 18:21   ` John Harrison
2025-06-12 18:29     ` Matthew Brost
2025-06-12 18:21   ` Matthew Brost
2025-06-12 18:26     ` John Harrison
2025-06-12 18:35       ` Matthew Brost
2025-06-12 18:05 ` [PATCH 2/2] drm/xe: Annotate default for guc_log_level param Lucas De Marchi
2025-06-12 18:26   ` John Harrison [this message]
2025-06-12 23:32 ` ✗ CI.checkpatch: warning for drm/xe: Tweak default GuC log level Patchwork
2025-06-12 23:34 ` ✓ CI.KUnit: success " Patchwork
2025-06-13  1:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-13 20:00 ` ✗ 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=b18ef656-adf9-4880-8839-c3484fe6ee8b@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michal.mrozek@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