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: Rodrigo Vivi <rodrigo.vivi@intel.com>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Drop useless d3cold allowed message
Date: Tue, 19 Nov 2024 14:03:34 -0800	[thread overview]
Message-ID: <Zz0LNv3K3fEm/o8R@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <o2qvrowghi5shepavwjzb6utpioyj2neqfbr45eny54fqrga3m@trovhcv4hoof>

On Tue, Nov 19, 2024 at 03:01:48PM -0600, Lucas De Marchi wrote:
> On Tue, Nov 19, 2024 at 01:50:20PM -0500, Rodrigo Vivi wrote:
> > On Fri, Nov 15, 2024 at 03:24:27PM -0800, Matthew Brost wrote:
> > > On Fri, Nov 15, 2024 at 04:53:04PM -0500, Rodrigo Vivi wrote:
> > > > On Fri, Nov 15, 2024 at 11:21:55AM -0800, Matthew Brost wrote:
> > > > > This message just spams dmesg providing little benefit. Remove it.
> > > >
> > > > I don't believe it is useless, but I also hate the spammers...
> > > >
> > > > perhaps we could bring the status of it in some debugfs form
> > > > as a replacement?
> > > >
> > > 
> > > ftrace could an option so if you really care about this enable it there?
> > 
> > hmmm it looks like a good idea... but no strong preference from my side...
> 
> as long as we are talking about adding a tracepoint rather than a plain
> trace_printk() unconditionally.
> 

Yes, trace point rather than trace_printk as that would just spam the
trace buffer.

> with dynamic debug we could use a verbose level that is only enabled per
> file when needed. Then we can keep messages like this rather than
> misusing the trace buffer.
> 

'with dynamic debug' - Can you explain what you mean here?

Matt

> Lucas De Marchi

  reply	other threads:[~2024-11-19 22:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 19:21 [PATCH] drm/xe: Drop useless d3cold allowed message Matthew Brost
2024-11-15 19:26 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-15 19:27 ` ✓ CI.checkpatch: " Patchwork
2024-11-15 19:28 ` ✓ CI.KUnit: " Patchwork
2024-11-15 19:37 ` ✗ CI.Build: failure " Patchwork
2024-11-15 20:57 ` ✓ CI.Patch_applied: success for drm/xe: Drop useless d3cold allowed message (rev2) Patchwork
2024-11-15 20:57 ` ✓ CI.checkpatch: " Patchwork
2024-11-15 20:58 ` ✓ CI.KUnit: " Patchwork
2024-11-15 21:16 ` ✓ CI.Build: " Patchwork
2024-11-15 21:17 ` ✗ CI.Hooks: failure " Patchwork
2024-11-15 21:18 ` ✓ CI.checksparse: success " Patchwork
2024-11-15 21:38 ` ✗ CI.BAT: failure " Patchwork
2024-11-15 21:53 ` [PATCH] drm/xe: Drop useless d3cold allowed message Rodrigo Vivi
2024-11-15 23:24   ` Matthew Brost
2024-11-19 18:50     ` Rodrigo Vivi
2024-11-19 21:01       ` Lucas De Marchi
2024-11-19 22:03         ` Matthew Brost [this message]
2024-11-19 23:35           ` Lucas De Marchi
2024-11-16  2:41 ` ✗ CI.FULL: failure for drm/xe: Drop useless d3cold allowed message (rev2) Patchwork
2024-11-18 17:53 ` ✓ CI.Patch_applied: success for drm/xe: Drop useless d3cold allowed message (rev3) Patchwork
2024-11-18 17:53 ` ✓ CI.checkpatch: " Patchwork
2024-11-18 17:54 ` ✓ CI.KUnit: " Patchwork
2024-11-18 18:12 ` ✓ CI.Build: " Patchwork
2024-11-18 18:14 ` ✓ CI.Hooks: " Patchwork
2024-11-18 18:16 ` ✓ CI.checksparse: " Patchwork
2024-11-18 18:46 ` ✗ CI.BAT: failure " Patchwork
2024-11-19  0:06 ` ✗ 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=Zz0LNv3K3fEm/o8R@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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