public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v4 1/6] drm/i915/guc: add doorbell map to debugfs/i915_guc_info
Date: Thu,  7 Apr 2016 18:21:13 +0100	[thread overview]
Message-ID: <1460049678-21918-2-git-send-email-david.s.gordon@intel.com> (raw)
In-Reply-To: <1460049678-21918-1-git-send-email-david.s.gordon@intel.com>

To properly verify the driver->doorbell->GuC functionality, validation
needs to know how the driver has assigned the doorbell cache lines and
registers, so make them visible through debugfs.

Signed-off-by: Dave Gordon <david.s.gordon@intel.com>
---
 drivers/gpu/drm/i915/i915_debugfs.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
index be4bcdc..87a9f3e 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -2488,6 +2488,7 @@ static int i915_guc_info(struct seq_file *m, void *data)
 	struct i915_guc_client client = {};
 	struct intel_engine_cs *engine;
 	u64 total = 0;
+	int i;
 
 	if (!HAS_GUC_SCHED(dev_priv))
 		return 0;
@@ -2502,6 +2503,13 @@ static int i915_guc_info(struct seq_file *m, void *data)
 
 	mutex_unlock(&dev->struct_mutex);
 
+	seq_printf(m, "Doorbell map:\n");
+	for (i = 0; i < BITS_TO_LONGS(GUC_MAX_DOORBELLS) - 3; i += 4)
+		seq_printf(m, "\t%016lx %016lx %016lx %016lx\n",
+			guc.doorbell_bitmap[i], guc.doorbell_bitmap[i+1],
+			guc.doorbell_bitmap[i+2], guc.doorbell_bitmap[i+3]);
+	seq_printf(m, "Doorbell next cacheline: 0x%x\n\n", guc.db_cacheline);
+
 	seq_printf(m, "GuC total action count: %llu\n", guc.action_count);
 	seq_printf(m, "GuC action failure count: %u\n", guc.action_fail);
 	seq_printf(m, "GuC last action command: 0x%x\n", guc.action_cmd);
-- 
1.9.1

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

  reply	other threads:[~2016-04-07 17:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 17:21 [PATCH v4 0/6] Fixes and workarounds for GuC/doorbell setup Dave Gordon
2016-04-07 17:21 ` Dave Gordon [this message]
2016-04-13 17:51   ` [PATCH v4 1/6] drm/i915/guc: add doorbell map to debugfs/i915_guc_info Yu Dai
2016-04-07 17:21 ` [PATCH v4 2/6] drm/i915/guc: move guc_ring_doorbell() nearer to callsite Dave Gordon
2016-04-13 17:52   ` Yu Dai
2016-04-07 17:21 ` [PATCH v4 3/6] drm/i915/guc: refactor doorbell management code Dave Gordon
2016-04-07 21:26   ` Yu Dai
2016-04-12  7:30     ` Dave Gordon
2016-04-07 17:21 ` [PATCH v4 4/6] drm/i915/guc: (re)initialise doorbell h/w when enabling GuC submission Dave Gordon
2016-04-13 17:50   ` Yu Dai
2016-04-13 19:46     ` Dave Gordon
2016-04-13 20:13       ` Yu Dai
2016-04-20 15:19         ` Dave Gordon
2016-04-07 17:21 ` [PATCH v4 5/6] drm/i915/guc: disable GuC submission earlier during GuC (re)load Dave Gordon
2016-04-13 17:51   ` Yu Dai
2016-04-07 17:21 ` [PATCH v4 6/6] DO NOT MERGE: add enable_guc_loading parameter Dave Gordon
2016-04-08  7:59 ` ✗ Fi.CI.BAT: failure for Fixes and workarounds for GuC/doorbell setup Patchwork
2016-04-20 15:28   ` Dave Gordon

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=1460049678-21918-2-git-send-email-david.s.gordon@intel.com \
    --to=david.s.gordon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox