From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Cc: daniele.ceraolospurio@intel.com, john.c.harrison@intel.com,
michal.wajdeczko@intel.com
Subject: [PATCH 2/2] drm/i915/guc: Print CT descriptor status in CT debug function
Date: Thu, 20 Jan 2022 10:36:55 -0800 [thread overview]
Message-ID: <20220120183655.3228-3-matthew.brost@intel.com> (raw)
In-Reply-To: <20220120183655.3228-1-matthew.brost@intel.com>
Noticed that the CT descriptor status was not printed in the CT debug
function, add that in.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
index 948cf31429412..5df2e3413796e 100644
--- a/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
+++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
@@ -1219,10 +1219,14 @@ void intel_guc_ct_print_info(struct intel_guc_ct *ct,
ct->ctbs.send.desc->head);
drm_printf(p, "Tail: %u\n",
ct->ctbs.send.desc->tail);
+ drm_printf(p, "Status: %u\n",
+ ct->ctbs.send.desc->status);
drm_printf(p, "G2H Space: %u\n",
atomic_read(&ct->ctbs.recv.space) * 4);
drm_printf(p, "Head: %u\n",
ct->ctbs.recv.desc->head);
drm_printf(p, "Tail: %u\n",
ct->ctbs.recv.desc->tail);
+ drm_printf(p, "Status: %u\n",
+ ct->ctbs.recv.desc->status);
}
--
2.34.1
prev parent reply other threads:[~2022-01-20 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 18:36 [PATCH 0/2] A few CT updates Matthew Brost
2022-01-20 18:36 ` [PATCH 1/2] drm/i915/guc: Don't check CT descriptor status before CT write / read Matthew Brost
2022-01-21 7:28 ` Jani Nikula
2022-01-21 21:03 ` Matthew Brost
2022-01-24 13:07 ` Jani Nikula
2022-01-20 18:36 ` Matthew Brost [this message]
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=20220120183655.3228-3-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=michal.wajdeczko@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