public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: jeff.mcgee@intel.com
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 2/2] drm/i915: Include current seqno in debugfs i915_gem_request
Date: Fri, 13 Oct 2017 13:10:33 -0700	[thread overview]
Message-ID: <20171013201033.29092-2-jeff.mcgee@intel.com> (raw)
In-Reply-To: <20171013201033.29092-1-jeff.mcgee@intel.com>

From: Jeff McGee <jeff.mcgee@intel.com>

Debugfs i915_gem_request lists the entire queue of requests on the
engine timeline. This will include requests that are complete but not
yet removed from the timeline. So let's include in this snapshot the
current seqno to help separate completed from pending.

Signed-off-by: Jeff McGee <jeff.mcgee@intel.com>
---
 drivers/gpu/drm/i915/i915_debugfs.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
index 135828fb1904..36d21f3c31ee 100644
--- a/drivers/gpu/drm/i915/i915_debugfs.c
+++ b/drivers/gpu/drm/i915/i915_debugfs.c
@@ -670,7 +670,9 @@ static int i915_gem_request_info(struct seq_file *m, void *data)
 			count++;
 
 		if (count) {
-			seq_printf(m, "%s requests: %d\n", engine->name, count);
+			seq_printf(m, "%s: requests %d, current seqno %x\n",
+				   engine->name, count,
+				   intel_engine_get_seqno(engine));
 			list_for_each_entry(req, &engine->timeline->requests, link)
 				print_request(m, req, "    ");
 			any++;
-- 
2.14.2

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

  reply	other threads:[~2017-10-13 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 20:10 [PATCH 1/2] drm/i915: Properly lock the engine timeline in debugfs i915_gem_request jeff.mcgee
2017-10-13 20:10 ` jeff.mcgee [this message]
2017-10-13 20:22 ` Chris Wilson
2017-10-13 21:26 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2017-10-14  8:49 ` ✓ Fi.CI.IGT: " 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=20171013201033.29092-2-jeff.mcgee@intel.com \
    --to=jeff.mcgee@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