All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH v2 0/5] drm/i915: error capture cleanups and refactor
Date: Wed,  9 Apr 2025 17:23:42 +0300	[thread overview]
Message-ID: <cover.1744208554.git.jani.nikula@intel.com> (raw)

v2 of [1] addressing Ville's feedback.

BR,
Jani.


[1] https://lore.kernel.org/r/20250325125954.1805212-1-jani.nikula@intel.com


Jani Nikula (5):
  drm/i915: use 32-bit access for gen2 irq registers
  drm/i915: record GEN2_IER in gtier[0] for pre-ilk error capture
  drm/i915: stop recording IER in error capture
  drm/i915: use display snapshot mechanism for display irq regs
  drm/i915: use graphics version instead of PCH split in error capture

 .../gpu/drm/i915/display/intel_display_irq.c  | 28 +++++++++++++++
 .../gpu/drm/i915/display/intel_display_irq.h  |  5 +++
 .../drm/i915/display/intel_display_snapshot.c |  5 +++
 drivers/gpu/drm/i915/i915_gpu_error.c         | 35 +++----------------
 drivers/gpu/drm/i915/i915_gpu_error.h         |  2 --
 5 files changed, 42 insertions(+), 33 deletions(-)

-- 
2.39.5


             reply	other threads:[~2025-04-09 14:23 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 14:23 Jani Nikula [this message]
2025-04-09 14:23 ` [PATCH v2 1/5] drm/i915: use 32-bit access for gen2 irq registers Jani Nikula
2025-04-10 16:13   ` Ville Syrjälä
2025-04-09 14:23 ` [PATCH v2 2/5] drm/i915: record GEN2_IER in gtier[0] for pre-ilk error capture Jani Nikula
2025-04-10 16:15   ` Ville Syrjälä
2025-04-09 14:23 ` [PATCH v2 3/5] drm/i915: stop recording IER in " Jani Nikula
2025-04-10 16:16   ` Ville Syrjälä
2025-04-09 14:23 ` [PATCH v2 4/5] drm/i915: use display snapshot mechanism for display irq regs Jani Nikula
2025-04-10 16:26   ` Ville Syrjälä
2025-04-11  7:09   ` [PATCH v3] " Jani Nikula
2025-04-09 14:23 ` [PATCH v2 5/5] drm/i915: use graphics version instead of PCH split in error capture Jani Nikula
2025-04-11  9:45   ` Jani Nikula
2025-04-11 13:39   ` Ville Syrjälä
2025-04-09 14:39 ` ✓ CI.Patch_applied: success for drm/i915: error capture cleanups and refactor Patchwork
2025-04-09 14:40 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-09 14:41 ` ✓ CI.KUnit: success " Patchwork
2025-04-09 14:57 ` ✗ CI.Build: failure " Patchwork
2025-04-09 14:59 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-04-09 14:59 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-09 15:24 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-09 23:37 ` ✗ i915.CI.Full: failure " Patchwork
2025-04-10  8:20 ` ✓ CI.Patch_applied: success " Patchwork
2025-04-10  8:20 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-10  8:21 ` ✓ CI.KUnit: success " Patchwork
2025-04-10  8:30 ` ✓ CI.Build: " Patchwork
2025-04-10  8:32 ` ✓ CI.Hooks: " Patchwork
2025-04-10  8:34 ` ✗ CI.checksparse: warning " Patchwork
2025-04-10  8:53 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-10 10:57 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-11  7:08 ` [PATCH] drm/i915: don't capture DERRMR for VLV/CHV Jani Nikula
2025-04-11  7:15   ` Ville Syrjälä
2025-04-11  7:15 ` ✓ CI.Patch_applied: success for drm/i915: don't capture DERRMR for VLV/CHV (rev2) Patchwork
2025-04-11  7:15 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-11  7:16 ` ✓ CI.KUnit: success " Patchwork
2025-04-11  7:24 ` ✓ CI.Build: " Patchwork
2025-04-11  7:27 ` ✓ CI.Hooks: " Patchwork
2025-04-11  7:28 ` ✗ CI.checksparse: warning " Patchwork
2025-04-11  7:47 ` ✓ Xe.CI.BAT: success " Patchwork
2025-04-11  9:00 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2025-04-11  9:00 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-11  9:27 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-11  9:47 ` ✗ 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=cover.1744208554.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.