All of lore.kernel.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>, Daniel Charles <daniel.charles@intel.com>
Subject: [PATCH] drm/xe: expose multi_lrc_mask in debugfs info
Date: Tue, 24 Mar 2026 14:23:48 -0700	[thread overview]
Message-ID: <20260324212348.4142888-1-x.wang@intel.com> (raw)

Add multi_lrc_mask to the per-device info printed via debugfs
(/sys/kernel/debug/dri/<N>/info). This value indicates which engine
classes support multi-LRC submission and varies across platforms.

Exposing it through debugfs allows userspace tools like IGT to query
the actual kernel configuration rather than hardcoding platform-specific
values in test code. This avoids duplicating KMD logic in IGT and makes
tests automatically adapt to platform differences.

Cc: Daniel Charles <daniel.charles@intel.com>
Signed-off-by: Xin Wang <x.wang@intel.com>
---
 drivers/gpu/drm/xe/xe_debugfs.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/xe/xe_debugfs.c b/drivers/gpu/drm/xe/xe_debugfs.c
index 844cfafe1ec7..32f03b2777d5 100644
--- a/drivers/gpu/drm/xe/xe_debugfs.c
+++ b/drivers/gpu/drm/xe/xe_debugfs.c
@@ -88,6 +88,7 @@ static int info(struct seq_file *m, void *data)
 	drm_printf(&p, "has_flat_ccs %s\n", str_yes_no(xe->info.has_flat_ccs));
 	drm_printf(&p, "has_usm %s\n", str_yes_no(xe->info.has_usm));
 	drm_printf(&p, "skip_guc_pc %s\n", str_yes_no(xe->info.skip_guc_pc));
+	drm_printf(&p, "multi_lrc_mask 0x%x\n", xe->info.multi_lrc_mask);
 	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));
-- 
2.43.0


             reply	other threads:[~2026-03-24 21:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 21:23 Xin Wang [this message]
2026-03-24 21:29 ` ✓ CI.KUnit: success for drm/xe: expose multi_lrc_mask in debugfs info 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   ` [PATCH v5 1/2] drm/xe: improve readability of debugfs engine info output Xin Wang
2026-04-02 16:29   ` [PATCH v5 2/2] drm/xe: expose multi-lrc engine classes in debugfs info 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

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=20260324212348.4142888-1-x.wang@intel.com \
    --to=x.wang@intel.com \
    --cc=daniel.charles@intel.com \
    --cc=intel-xe@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.