Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: <John.C.Harrison@intel.com>
Cc: Intel-GFX@lists.freedesktop.org, DRI-Devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/2] Add support for dumping error captures via kernel logging
Date: Tue, 11 Apr 2023 10:41:37 -0400	[thread overview]
Message-ID: <ZDVxocPZR1Ad2QLa@intel.com> (raw)
In-Reply-To: <20230410192523.2020049-1-John.C.Harrison@Intel.com>

On Mon, Apr 10, 2023 at 12:25:21PM -0700, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
> 
> Sometimes, the only effective way to debug an issue is to dump all the
> interesting information at the point of failure. So add support for
> doing that.

No! Please no!
We have some of this on Xe and I'm hating it. I'm going to try to remove
from there soon. It is horrible when you lost the hability to use dmesg
directly because it goes over the number of lines it saves... or even
with dmesg -w it goes over the number of lines of your terminal...
or the ssh and serial slowness when printing a bunch of information.

We probably want to be able to capture multiple error states and be
able to cross them with a kernel timeline, but definitely not overflood
our log terminals.

> 
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> 
> 
> John Harrison (2):
>   drm/i915: Dump error capture to kernel log
>   drm/i915/guc: Dump error capture to dmesg on CTB error
> 
>  drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c |  53 +++++++++
>  drivers/gpu/drm/i915/gt/uc/intel_guc_ct.h |   6 +
>  drivers/gpu/drm/i915/i915_gpu_error.c     | 130 ++++++++++++++++++++++
>  drivers/gpu/drm/i915/i915_gpu_error.h     |   8 ++
>  4 files changed, 197 insertions(+)
> 
> -- 
> 2.39.1
> 

  parent reply	other threads:[~2023-04-11 14:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 19:25 [Intel-gfx] [PATCH 0/2] Add support for dumping error captures via kernel logging John.C.Harrison
2023-04-10 19:25 ` [Intel-gfx] [PATCH 1/2] drm/i915: Dump error capture to kernel log John.C.Harrison
2023-04-10 19:25 ` [Intel-gfx] [PATCH 2/2] drm/i915/guc: Dump error capture to dmesg on CTB error John.C.Harrison
2023-04-10 19:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add support for dumping error captures via kernel logging Patchwork
2023-04-10 19:50 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-10 19:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-10 21:15 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-04-11 14:41 ` Rodrigo Vivi [this message]
2023-04-11 16:41   ` [Intel-gfx] [PATCH 0/2] " John Harrison
2023-04-11 16:50     ` Daniel Vetter
2023-04-18 16:38       ` Rodrigo Vivi

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=ZDVxocPZR1Ad2QLa@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=DRI-Devel@lists.freedesktop.org \
    --cc=Intel-GFX@lists.freedesktop.org \
    --cc=John.C.Harrison@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