From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>, <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] drm/i915/display: add snapshot capture/print infra
Date: Thu, 5 Sep 2024 13:01:57 -0400 [thread overview]
Message-ID: <ZtnkBd9k4zGM6DRo@intel.com> (raw)
In-Reply-To: <cover.1725372032.git.jani.nikula@intel.com>
On Tue, Sep 03, 2024 at 05:02:56PM +0300, Jani Nikula wrote:
> Add display capture/print infra to abstract it from i915 gpu error state
> capture, and prepare for perhaps bolting it into xe devcoredump in the
> future.
One thing that just occurred to me now is that perhaps we don't want
to add that to the xe devcoredump itself, but make display having it's
own coredump virtual device?
Do we really need to dump only when GT is hang? Or perhaps adding more
useful information on display and print on display goof-ups?
But anyway, it could be orthogonal and Xe also use these display functions
on gpu hang as well. Nice work!
>
> BR,
> Jani.
>
>
> Jani Nikula (4):
> drm/i915: dump display parameters captured in error state, not current
> drm/i915/display: add intel_display_snapshot abstraction
> drm/i915/display: move device info and params handling to snapshot
> drm/i915/display: move dmc snapshotting to new display snapshot
>
> drivers/gpu/drm/i915/Makefile | 1 +
> .../drm/i915/display/intel_display_params.c | 8 ++-
> .../drm/i915/display/intel_display_params.h | 5 +-
> .../drm/i915/display/intel_display_snapshot.c | 72 +++++++++++++++++++
> .../drm/i915/display/intel_display_snapshot.h | 16 +++++
> drivers/gpu/drm/i915/display/intel_dmc.c | 39 +++++++---
> drivers/gpu/drm/i915/display/intel_dmc.h | 7 +-
> drivers/gpu/drm/i915/display/intel_overlay.c | 16 +++--
> drivers/gpu/drm/i915/display/intel_overlay.h | 19 ++---
> drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
> drivers/gpu/drm/i915/i915_gpu_error.c | 25 ++-----
> drivers/gpu/drm/i915/i915_gpu_error.h | 11 +--
> 12 files changed, 162 insertions(+), 59 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/display/intel_display_snapshot.c
> create mode 100644 drivers/gpu/drm/i915/display/intel_display_snapshot.h
>
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-09-05 17:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 14:02 [PATCH 0/4] drm/i915/display: add snapshot capture/print infra Jani Nikula
2024-09-03 14:02 ` [PATCH 1/4] drm/i915: dump display parameters captured in error state, not current Jani Nikula
2024-09-05 16:43 ` Rodrigo Vivi
2024-09-03 14:02 ` [PATCH 2/4] drm/i915/display: add intel_display_snapshot abstraction Jani Nikula
2024-09-04 12:23 ` kernel test robot
2024-09-04 13:04 ` kernel test robot
2024-09-04 14:19 ` [PATCH v2] " Jani Nikula
2024-09-05 16:55 ` Rodrigo Vivi
2024-09-03 14:02 ` [PATCH 3/4] drm/i915/display: move device info and params handling to snapshot Jani Nikula
2024-09-05 16:56 ` Rodrigo Vivi
2024-09-03 14:03 ` [PATCH 4/4] drm/i915/display: move dmc snapshotting to new display snapshot Jani Nikula
2024-09-05 16:59 ` Rodrigo Vivi
2024-09-03 19:22 ` ✓ CI.Patch_applied: success for drm/i915/display: add snapshot capture/print infra Patchwork
2024-09-03 19:22 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-03 19:24 ` ✓ CI.KUnit: success " Patchwork
2024-09-03 19:36 ` ✓ CI.Build: " Patchwork
2024-09-03 19:38 ` ✓ CI.Hooks: " Patchwork
2024-09-03 19:39 ` ✗ CI.checksparse: warning " Patchwork
2024-09-03 19:58 ` ✓ CI.BAT: success " Patchwork
2024-09-03 22:34 ` ✗ CI.FULL: failure " Patchwork
2024-09-04 14:25 ` ✓ CI.Patch_applied: success for drm/i915/display: add snapshot capture/print infra (rev2) Patchwork
2024-09-04 14:25 ` ✗ CI.checkpatch: warning " Patchwork
2024-09-04 14:26 ` ✓ CI.KUnit: success " Patchwork
2024-09-04 14:38 ` ✓ CI.Build: " Patchwork
2024-09-04 14:40 ` ✓ CI.Hooks: " Patchwork
2024-09-04 14:42 ` ✗ CI.checksparse: warning " Patchwork
2024-09-04 15:18 ` ✗ CI.BAT: failure " Patchwork
2024-09-05 17:01 ` Rodrigo Vivi [this message]
2024-09-06 13:43 ` ✓ CI.FULL: success " 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=ZtnkBd9k4zGM6DRo@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).