From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 3/5] drm/i915: stop recording IER in error capture
Date: Thu, 10 Apr 2025 19:16:29 +0300 [thread overview]
Message-ID: <Z_fu3fm0b35BrZm1@intel.com> (raw)
In-Reply-To: <d91b9668369bec152cea2576c45acf15db809df5.1744208554.git.jani.nikula@intel.com>
On Wed, Apr 09, 2025 at 05:23:45PM +0300, Jani Nikula wrote:
> With pre-ilk GEN2_IER capture moved to gtier[0], the remaining IER
> aren't all that relevant. Stop capturing them.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_gpu_error.c | 8 --------
> drivers/gpu/drm/i915/i915_gpu_error.h | 1 -
> 2 files changed, 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 64c760e7b7ee..50cd0c433e6d 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -729,7 +729,6 @@ static void err_print_gt_info(struct drm_i915_error_state_buf *m,
> static void err_print_gt_display(struct drm_i915_error_state_buf *m,
> struct intel_gt_coredump *gt)
> {
> - err_printf(m, "IER: 0x%08x\n", gt->ier);
I don't think the tools should care about this being there.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> err_printf(m, "DERRMR: 0x%08x\n", gt->derrmr);
> }
>
> @@ -1775,13 +1774,6 @@ static void gt_record_display_regs(struct intel_gt_coredump *gt)
>
> if (DISPLAY_VER(i915) >= 6 && DISPLAY_VER(i915) < 20)
> gt->derrmr = intel_uncore_read(uncore, DERRMR);
> -
> - if (GRAPHICS_VER(i915) >= 8)
> - gt->ier = intel_uncore_read(uncore, GEN8_DE_MISC_IER);
> - else if (IS_VALLEYVIEW(i915))
> - gt->ier = intel_uncore_read(uncore, VLV_IER);
> - else if (HAS_PCH_SPLIT(i915))
> - gt->ier = intel_uncore_read(uncore, DEIER);
> }
>
> /* Capture all other registers that GuC doesn't capture. */
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.h b/drivers/gpu/drm/i915/i915_gpu_error.h
> index 749e1c55613e..ac55603a81d7 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.h
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.h
> @@ -146,7 +146,6 @@ struct intel_gt_coredump {
> /* Generic register state */
> u32 eir;
> u32 pgtbl_er;
> - u32 ier;
> u32 gtier[6], ngtier;
> u32 forcewake;
> u32 error; /* gen6+ */
> --
> 2.39.5
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-04-10 16:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 14:23 [PATCH v2 0/5] drm/i915: error capture cleanups and refactor Jani Nikula
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ä [this message]
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:59 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: error capture cleanups and refactor 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-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 9:00 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: don't capture DERRMR for VLV/CHV (rev2) Patchwork
2025-04-11 9:00 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-11 9:27 ` ✓ i915.CI.BAT: 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=Z_fu3fm0b35BrZm1@intel.com \
--to=ville.syrjala@linux.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