From: Stuart Summers <stuart.summers@intel.com>
Cc: intel-xe@lists.freedesktop.org, rodrigo.vivi@intel.com,
matthew.d.roper@intel.com, gustavo.sousa@intel.com,
Stuart Summers <stuart.summers@intel.com>
Subject: [PATCH 0/8] Set up for debug configfs group
Date: Thu, 12 Nov 2026 21:35:05 +0000 [thread overview]
Message-ID: <20261112213508.457213-10-stuart.summers@intel.com> (raw)
Splitting out patches from [1] which have already been
reviewed to get CI results and get these merged. I'll
send out an updated series with the rest of the patches
after.
Note that I removed the "Assisted-by: LLM" attribution
per latest requirements. I also made some minor changes
around the rebase - mostly dropping the fallback functions
since those were removed. There was also a new function
added for the disable vram page offline configfs, so that
function was rebased in to this series as well.
Everything here has an R-B already.
[1]: https://patchwork.freedesktop.org/series/165879/#rev10
Stuart Summers (8):
drm/xe: Guard configfs attribute reads in getters
drm/xe/configfs: Fix out-of-bounds read in parse_wa_bb_lines()
drm/xe/configfs: Copy wa_bb out under the configfs lock
drm/xe: Invert vram_page_offline configfs attribute
drm/xe: Make survivability_mode configfs attribute a bitmap
drm/xe: Sort xe_config_device fields
drm/xe: Split out configfs data structures
drm/xe: Add a new debug focused configfs group
drivers/gpu/drm/xe/Makefile | 3 +
drivers/gpu/drm/xe/xe_configfs.c | 1299 ++++++++++----------
drivers/gpu/drm/xe/xe_configfs.h | 35 +-
drivers/gpu/drm/xe/xe_configfs_debug.c | 14 +
drivers/gpu/drm/xe/xe_configfs_debug.h | 13 +
drivers/gpu/drm/xe/xe_configfs_types.h | 58 +
drivers/gpu/drm/xe/xe_lrc.c | 38 +-
drivers/gpu/drm/xe/xe_ras.c | 18 +-
drivers/gpu/drm/xe/xe_ras.h | 2 +-
drivers/gpu/drm/xe/xe_ras_types.h | 4 +-
drivers/gpu/drm/xe/xe_survivability_mode.c | 7 +-
drivers/gpu/drm/xe/xe_ttm_vram_mgr.c | 2 +-
12 files changed, 798 insertions(+), 695 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_configfs_debug.c
create mode 100644 drivers/gpu/drm/xe/xe_configfs_debug.h
create mode 100644 drivers/gpu/drm/xe/xe_configfs_types.h
--
2.43.0
next reply other threads:[~2026-11-12 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 21:35 Stuart Summers [this message]
2026-11-12 21:35 ` [PATCH 1/8] drm/xe: Guard configfs attribute reads in getters Stuart Summers
2026-11-12 21:35 ` [PATCH 2/8] drm/xe/configfs: Fix out-of-bounds read in parse_wa_bb_lines() Stuart Summers
2026-11-12 21:35 ` [PATCH 3/8] drm/xe/configfs: Copy wa_bb out under the configfs lock Stuart Summers
2026-11-12 21:35 ` [PATCH 4/8] drm/xe: Invert vram_page_offline configfs attribute Stuart Summers
2026-11-12 21:35 ` [PATCH 5/8] drm/xe: Make survivability_mode configfs attribute a bitmap Stuart Summers
2026-11-12 21:35 ` [PATCH 6/8] drm/xe: Sort xe_config_device fields Stuart Summers
2026-11-12 21:35 ` [PATCH 7/8] drm/xe: Split out configfs data structures Stuart Summers
2026-11-12 21:35 ` [PATCH 8/8] drm/xe: Add a new debug focused configfs group Stuart Summers
2026-11-12 21:42 ` ✗ CI.checkpatch: warning for Set up for debug " Patchwork
2026-11-12 21:44 ` ✓ CI.KUnit: success " Patchwork
2026-11-12 22:15 ` ✓ 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=20261112213508.457213-10-stuart.summers@intel.com \
--to=stuart.summers@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@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 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.