Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: lucas.demarchi@intel.com, intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2 1/2] drm/xe/execlist: Remove leftover printk messages
Date: Wed, 19 Jul 2023 11:28:43 -0400	[thread overview]
Message-ID: <ZLgBKwPAuBbDx83n@intel.com> (raw)
In-Reply-To: <20230719135108.7-2-francois.dugast@intel.com>

On Wed, Jul 19, 2023 at 01:51:07PM +0000, Francois Dugast wrote:
> Those look like leftover debug and are not even being used. If they were
> real debug/info, they should be using the drm helpers.
> 
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_execlist.c | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_execlist.c b/drivers/gpu/drm/xe/xe_execlist.c
> index 46293c9bb6a8..3aec37985f32 100644
> --- a/drivers/gpu/drm/xe/xe_execlist.c
> +++ b/drivers/gpu/drm/xe/xe_execlist.c
> @@ -47,8 +47,6 @@ static void __start_lrc(struct xe_hw_engine *hwe, struct xe_lrc *lrc,
>  	struct xe_device *xe = gt_to_xe(gt);
>  	u64 lrc_desc;
>  
> -	printk(KERN_INFO "__start_lrc(%s, 0x%p, %u)\n", hwe->name, lrc, ctx_id);
> -
>  	lrc_desc = xe_lrc_descriptor(lrc);
>  
>  	if (GRAPHICS_VERx100(xe) >= 1250) {
> @@ -125,9 +123,6 @@ static void __xe_execlist_port_idle(struct xe_execlist_port *port)
>  	if (!port->running_exl)
>  		return;
>  
> -	printk(KERN_INFO "__xe_execlist_port_idle(%d:%d)\n", port->hwe->class,
> -	       port->hwe->instance);
> -
>  	xe_lrc_write_ring(&port->hwe->kernel_lrc, noop, sizeof(noop));
>  	__start_lrc(port->hwe, &port->hwe->kernel_lrc, 0);
>  	port->running_exl = NULL;
> @@ -176,9 +171,6 @@ static u64 read_execlist_status(struct xe_hw_engine *hwe)
>  	lo = xe_mmio_read32(gt, RING_EXECLIST_STATUS_LO(hwe->mmio_base));
>  	hi = xe_mmio_read32(gt, RING_EXECLIST_STATUS_HI(hwe->mmio_base));
>  
> -	printk(KERN_INFO "EXECLIST_STATUS %d:%d = 0x%08x %08x\n", hwe->class,
> -	       hwe->instance, hi, lo);

This one is indeed annoying when it happens, so we need to get rid of,
but I believe we need to have at least a big drm_info somewhere to let us
know that execlist is in place. Probably at execlist_engine_init ?!

> -
>  	return lo | (u64)hi << 32;
>  }
>  
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-07-19 15:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 13:51 [Intel-xe] [PATCH v2 0/2] drm/xe: Style cleanup Francois Dugast
2023-07-19 13:51 ` [Intel-xe] [PATCH v2 1/2] drm/xe/execlist: Remove leftover printk messages Francois Dugast
2023-07-19 15:28   ` Rodrigo Vivi [this message]
2023-07-19 16:14     ` Lucas De Marchi
2023-07-19 13:51 ` [Intel-xe] [PATCH v2 2/2] drm/xe: Cleanup style warnings and errors Francois Dugast
2023-07-19 15:25   ` Rodrigo Vivi
2023-07-19 15:39     ` Francois Dugast
2023-07-19 15:54       ` Rodrigo Vivi
2023-07-19 14:33 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Style cleanup Patchwork
2023-07-19 14:33 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-07-19 14:34 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-07-19 14:38 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-19 14:38 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-19 14:40 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-19 15:14 ` [Intel-xe] ○ CI.BAT: info " 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=ZLgBKwPAuBbDx83n@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --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