From: Xin Wang <x.wang@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Xin Wang <x.wang@intel.com>
Subject: [PATCH v5 0/2] drm/xe: expose multi_lrc_mask in debugfs info
Date: Thu, 2 Apr 2026 11:05:49 -0700 [thread overview]
Message-ID: <20260402180552.24121-1-x.wang@intel.com> (raw)
This series improves the debugfs info output for xe engines and exposes
the multi-LRC engine class capability.
Patch 1 replaces raw numeric engine masks with human-readable engine and
class names in the per-GT debugfs info output, making it easier for a
human to interpret directly and simpler for IGT tests to use when
validating engine capabilities.
Patch 2 adds multi_lrc_engine_classes to the device-level info output
as a useful extra piece of information for debugging.
v5: (Matt Roper)
- Reword commit messages to avoid "userspace" framing
- Use early-return pattern in print_engine_class_mask() and
print_engine_mask() to minimize indentation
Xin Wang (2):
drm/xe: improve readability of debugfs engine info output
drm/xe: expose multi-lrc engine classes in debugfs info
drivers/gpu/drm/xe/xe_debugfs.c | 43 ++++++++++++++++++++++++++++++---
1 file changed, 39 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-02 18:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 18:05 Xin Wang [this message]
2026-04-02 18:05 ` [PATCH v5 1/2] drm/xe: improve readability of debugfs engine info output Xin Wang
2026-04-02 18:05 ` [PATCH v5 2/2] drm/xe: expose multi-lrc engine classes in debugfs info Xin Wang
2026-04-02 18:46 ` ✓ CI.KUnit: success for drm/xe: expose multi_lrc_mask in debugfs info (rev6) Patchwork
2026-04-02 19:29 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-03 8:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-03 17:23 ` Matt Roper
-- strict thread matches above, loose matches on Subject: below --
2026-03-24 21:23 [PATCH] drm/xe: expose multi_lrc_mask in debugfs info Xin Wang
2026-04-02 16:29 ` [PATCH v5 0/2] " 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=20260402180552.24121-1-x.wang@intel.com \
--to=x.wang@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.