public inbox for intel-xe@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Xin Wang <x.wang@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Xin Wang <x.wang@intel.com>,
	Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH v5 1/2] drm/xe: improve readability of debugfs engine info output
Date: Thu,  2 Apr 2026 09:29:57 -0700	[thread overview]
Message-ID: <20260402162958.16924-2-x.wang@intel.com> (raw)
In-Reply-To: <20260402162958.16924-1-x.wang@intel.com>

Improve the readability of the info debugfs output by replacing
raw numeric engine masks with human-readable engine and class
names.

Also print per-GT engine capability data in a form that is easier
for a human to interpret directly, and as a side effect simpler
for IGT tests to use when validating engine capabilities.

Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Signed-off-by: Xin Wang <x.wang@intel.com>
---
 drivers/gpu/drm/xe/xe_debugfs.c | 41 +++++++++++++++++++++++++++++----
 1 file changed, 37 insertions(+), 4 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_debugfs.c b/drivers/gpu/drm/xe/xe_debugfs.c
index 844cfafe1ec7..490d7ef7e812 100644
--- a/drivers/gpu/drm/xe/xe_debugfs.c
+++ b/drivers/gpu/drm/xe/xe_debugfs.c
@@ -15,9 +15,11 @@
 #include "xe_bo.h"
 #include "xe_device.h"
 #include "xe_force_wake.h"
+#include "xe_gt.h"
 #include "xe_gt_debugfs.h"
 #include "xe_gt_printk.h"
 #include "xe_guc_ads.h"
+#include "xe_hw_engine.h"
 #include "xe_mmio.h"
 #include "xe_pm.h"
 #include "xe_psmi.h"
@@ -61,6 +63,37 @@ static struct xe_device *node_to_xe(struct drm_info_node *node)
 	return to_xe_device(node->minor->dev);
 }
 
+static void print_engine_class_mask(struct drm_printer *p, u16 mask)
+{
+	if (!mask) {
+		drm_printf(p, " none\n");
+		return;
+	}
+
+	for (enum xe_engine_class ec = 0; ec < XE_ENGINE_CLASS_MAX; ec++) {
+		if (mask & BIT(ec))
+			drm_printf(p, " %s", xe_hw_engine_class_to_str(ec));
+	}
+	drm_printf(p, "\n");
+}
+
+static void print_engine_mask(struct drm_printer *p, struct xe_gt *gt, u64 mask)
+{
+	struct xe_hw_engine *hwe;
+	enum xe_hw_engine_id id;
+
+	if (!mask) {
+		drm_printf(p, " none\n");
+		return;
+	}
+
+	for_each_hw_engine(hwe, gt, id) {
+		if (mask & BIT_ULL(id))
+			drm_printf(p, " %s", hwe->name);
+	}
+	drm_printf(p, "\n");
+}
+
 static int info(struct seq_file *m, void *data)
 {
 	struct xe_device *xe = node_to_xe(m->private);
@@ -91,10 +124,10 @@ static int info(struct seq_file *m, void *data)
 	for_each_gt(gt, xe, id) {
 		drm_printf(&p, "gt%d force wake %d\n", id,
 			   xe_force_wake_ref(gt_to_fw(gt), XE_FW_GT));
-		drm_printf(&p, "gt%d engine_mask 0x%llx\n", id,
-			   gt->info.engine_mask);
-		drm_printf(&p, "gt%d multi_queue_engine_class_mask 0x%x\n", id,
-			   gt->info.multi_queue_engine_class_mask);
+		drm_printf(&p, "gt%d engines", id);
+		print_engine_mask(&p, gt, gt->info.engine_mask);
+		drm_printf(&p, "gt%d multi_queue_engine_classes", id);
+		print_engine_class_mask(&p, gt->info.multi_queue_engine_class_mask);
 	}
 
 	return 0;
-- 
2.43.0


  reply	other threads:[~2026-04-02 16:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 21:23 [PATCH] drm/xe: expose multi_lrc_mask in debugfs info Xin Wang
2026-03-24 21:29 ` ✓ CI.KUnit: success for " Patchwork
2026-03-24 22:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-25 10:40 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-30 17:09 ` [PATCH v2] drm/xe: expose multi_lrc_engine_classes " Xin Wang
2026-04-01 21:08   ` Matt Roper
2026-03-30 17:16 ` ✓ CI.KUnit: success for drm/xe: expose multi_lrc_mask in debugfs info (rev2) Patchwork
2026-03-30 17:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-30 20:49 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-31  0:29 ` [PATCH v3] drm/xe: improve readability of debugfs info engine output Xin Wang
2026-03-31  3:29   ` Niranjana Vishwanathapura
2026-03-31  0:43 ` ✓ CI.KUnit: success for drm/xe: expose multi_lrc_mask in debugfs info (rev3) Patchwork
2026-03-31  1:29 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-31  5:56 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-01 21:26 ` [PATCH v4 0/2] drm/xe: expose multi_lrc_mask in debugfs info Xin Wang
2026-04-01 21:26   ` [PATCH v4 1/2] drm/xe: improve readability of debugfs engine info output Xin Wang
2026-04-01 22:29     ` Matt Roper
2026-04-01 21:26   ` [PATCH v4 2/2] drm/xe: expose multi-lrc engine classes in debugfs info Xin Wang
2026-04-01 22:33     ` Matt Roper
2026-04-01 21:33 ` ✓ CI.KUnit: success for drm/xe: expose multi_lrc_mask in debugfs info (rev4) Patchwork
2026-04-01 22:10 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-02  5:16 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-02 16:29 ` [PATCH v5 0/2] drm/xe: expose multi_lrc_mask in debugfs info Xin Wang
2026-04-02 16:29   ` Xin Wang [this message]
2026-04-02 16:29   ` [PATCH v5 2/2] drm/xe: expose multi-lrc engine classes " Xin Wang
2026-04-02 16:49 ` ✓ CI.KUnit: success for drm/xe: expose multi_lrc_mask in debugfs info (rev5) Patchwork
2026-04-02 17:45 ` ✓ Xe.CI.BAT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2026-04-02 18:05 [PATCH v5 0/2] drm/xe: expose multi_lrc_mask in debugfs info Xin Wang
2026-04-02 18:05 ` [PATCH v5 1/2] drm/xe: improve readability of debugfs engine info output Xin Wang

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=20260402162958.16924-2-x.wang@intel.com \
    --to=x.wang@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=niranjana.vishwanathapura@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