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>
Subject: [PATCH v5 0/2] drm/xe: expose multi_lrc_mask in debugfs info
Date: Thu,  2 Apr 2026 09:29:56 -0700	[thread overview]
Message-ID: <20260402162958.16924-1-x.wang@intel.com> (raw)
In-Reply-To: <20260324212348.4142888-1-x.wang@intel.com>

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


  parent 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 ` Xin Wang [this message]
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
  -- 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

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-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox