All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v5 4/6] drm/i915: add rcs topology to error state
Date: Tue, 16 Jan 2018 13:40:08 +0000	[thread overview]
Message-ID: <20180116134010.20307-5-lionel.g.landwerlin@intel.com> (raw)
In-Reply-To: <20180116134010.20307-1-lionel.g.landwerlin@intel.com>

This might be useful information for developers looking at an error
state.

v2: Place topology towards the end of the error state (Chris)

v3: Reuse common printing code (Michal)

Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
 drivers/gpu/drm/i915/i915_gpu_error.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
index 944059322daa..aaa34a2bebe1 100644
--- a/drivers/gpu/drm/i915/i915_gpu_error.c
+++ b/drivers/gpu/drm/i915/i915_gpu_error.c
@@ -605,6 +605,14 @@ static void err_print_uc(struct drm_i915_error_state_buf *m,
 	print_error_obj(m, NULL, "GuC log buffer", error_uc->guc_log);
 }
 
+static void err_print_rcs_topology(struct drm_i915_error_state_buf *m,
+				   const struct sseu_dev_info *sseu)
+{
+	struct drm_printer p = i915_error_printer(m);
+
+	intel_device_info_dump_topology(sseu, &p);
+}
+
 int i915_error_state_to_str(struct drm_i915_error_state_buf *m,
 			    const struct i915_gpu_state *error)
 {
@@ -787,6 +795,7 @@ int i915_error_state_to_str(struct drm_i915_error_state_buf *m,
 		intel_display_print_error_state(m, error->display);
 
 	err_print_capabilities(m, &error->device_info);
+	err_print_rcs_topology(m, &INTEL_INFO(dev_priv)->sseu);
 	err_print_params(m, &error->params);
 	err_print_uc(m, &error->uc);
 
-- 
2.15.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-01-16 13:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 13:40 [PATCH v5 0/6] drm/i915: expose RCS topology to userspace Lionel Landwerlin
2018-01-16 13:40 ` [PATCH v5 1/6] drm/i915: store all subslice masks Lionel Landwerlin
2018-01-16 13:40 ` [PATCH v5 2/6] drm/i915/debugfs: reuse max slice/subslices already stored in sseu Lionel Landwerlin
2018-01-16 13:40 ` [PATCH v5 3/6] drm/i915/debugfs: add rcs topology entry Lionel Landwerlin
2018-01-16 13:40 ` Lionel Landwerlin [this message]
2018-01-16 13:57   ` [PATCH v5 4/6] drm/i915: add rcs topology to error state Chris Wilson
2018-01-16 14:14     ` Lionel Landwerlin
2018-01-16 13:40 ` [PATCH v5 5/6] drm/i915: add query uAPI Lionel Landwerlin
2018-01-16 14:08   ` Chris Wilson
2018-01-16 14:31     ` Lionel Landwerlin
2018-01-16 13:40 ` [PATCH v5 6/6] drm/i915: expose rcs topology through " Lionel Landwerlin
2018-01-16 14:22   ` Chris Wilson
2018-01-16 14:48     ` Lionel Landwerlin
2018-01-16 14:40 ` ✓ Fi.CI.BAT: success for drm/i915: expose RCS topology to userspace Patchwork
2018-01-16 16:39 ` ✗ Fi.CI.IGT: warning " 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=20180116134010.20307-5-lionel.g.landwerlin@intel.com \
    --to=lionel.g.landwerlin@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.