All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: mallesh.koujalagi@intel.com,
	Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
Subject: [PATCH v5 00/12] drm/xe: Convert IO_BUS errors to structured xe_log API
Date: Thu,  8 Oct 2026 02:44:05 +0530	[thread overview]
Message-ID: <20261007211417.2093611-1-dnyaneshwar.bhadane@intel.com> (raw)

This series meant for converitng the logs struct of IO_BUS device hardware
catergories with different components such as GT, RTP, HWWOM, REGS, PAT,
GT, LMTT, VRAM.

Patch 1 adds the new component definitions. Patches 2-12 convert individual
subsystems to use xe_log_err/xe_log_err_fatal/xe_log_info with the
appropriate component tags:

  - GGTT: Graphics stolen memory probe and configuration errors
  - HWMON: PCode readback and registration failures
  - MMIO/REGS/RTP: BAR mapping, save-restore and force-wake errors
  - MEMIRQ: Page allocation and GuC setup failures
  - PAT: Missing PAT table detection
  - GT: Unknown GMDID version reporting
  - LMTT: HW invalidation failures
  - VRAM: BAR validation and visibility errors

Dnyaneshwar Bhadane (12):
  drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components
  drm/xe/ggtt: Report GGTT errors using structured logging
  drm/xe/hwmon: Report errors using structured xe_log API
  drm/xe/mmio: Report BAR mapping errors using structured xe_log API
  drm/xe/memirq: Report errors using structured xe_log API
  drm/xe/reg_sr: Report save-restore errors using structured xe_log API
  drm/xe/pat: Return error from xe_pat_init_early() on unknown platform
  drm/xe/pat: Report missing PAT table using structured xe_log API
  drm/xe/pci: Report unknown GMDID versions using structured xe_log API
  drm/xe/lmtt: Report invalidation errors using structured xe_log API
  drm/xe/vram: Report tile vs device VRAM visibility errors
  drm/xe/vram: Report VRAM errors using structured xe_log API

 drivers/gpu/drm/xe/abi/xe_log_abi.h |  3 +++
 drivers/gpu/drm/xe/xe_device.c      |  4 +++-
 drivers/gpu/drm/xe/xe_ggtt.c        |  9 ++++++---
 drivers/gpu/drm/xe/xe_hwmon.c       | 15 +++++++++------
 drivers/gpu/drm/xe/xe_lmtt.c        | 10 ++++++----
 drivers/gpu/drm/xe/xe_memirq.c      |  7 ++++---
 drivers/gpu/drm/xe/xe_mmio.c        | 12 ++++++++----
 drivers/gpu/drm/xe/xe_pat.c         | 17 ++++++++++++++---
 drivers/gpu/drm/xe/xe_pat.h         |  4 +++-
 drivers/gpu/drm/xe/xe_pci.c         | 10 ++++++----
 drivers/gpu/drm/xe/xe_reg_sr.c      | 11 ++++++-----
 drivers/gpu/drm/xe/xe_vram.c        | 27 ++++++++++++++++-----------
 12 files changed, 84 insertions(+), 45 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-10-07 21:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 21:14 Dnyaneshwar Bhadane [this message]
2026-10-07 21:14 ` [PATCH v5 01/12] drm/xe/log: Add VRAM, PAT, and HWMON DRIVER_HARDWARE components Dnyaneshwar Bhadane
2026-10-08 13:59   ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 02/12] drm/xe/ggtt: Report GGTT errors using structured logging Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 03/12] drm/xe/hwmon: Report errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-08 13:01   ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 04/12] drm/xe/mmio: Report BAR mapping " Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 05/12] drm/xe/memirq: Report " Dnyaneshwar Bhadane
2026-10-07 21:20   ` sashiko-bot
2026-10-07 21:14 ` [PATCH v5 06/12] drm/xe/reg_sr: Report save-restore " Dnyaneshwar Bhadane
2026-10-07 21:23   ` sashiko-bot
2026-10-08 13:45   ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 07/12] drm/xe/pat: Return error from xe_pat_init_early() on unknown platform Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 08/12] drm/xe/pat: Report missing PAT table using structured xe_log API Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 09/12] drm/xe/pci: Report unknown GMDID versions " Dnyaneshwar Bhadane
2026-10-07 21:14 ` [PATCH v5 10/12] drm/xe/lmtt: Report invalidation errors " Dnyaneshwar Bhadane
2026-10-08 13:07   ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 11/12] drm/xe/vram: Report tile vs device VRAM visibility errors Dnyaneshwar Bhadane
2026-10-08 13:25   ` Mallesh, Koujalagi
2026-10-07 21:14 ` [PATCH v5 12/12] drm/xe/vram: Report VRAM errors using structured xe_log API Dnyaneshwar Bhadane
2026-10-07 21:19   ` sashiko-bot
2026-10-07 21:40 ` ✗ CI.checkpatch: warning for drm/xe: Convert IO_BUS errors to structured xe_log API (rev5) Patchwork
2026-10-07 21:42 ` ✓ CI.KUnit: success " Patchwork
2026-10-07 22:32 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-08  2:59 ` ✗ Xe.CI.FULL: failure " 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=20261007211417.2093611-1-dnyaneshwar.bhadane@intel.com \
    --to=dnyaneshwar.bhadane@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=mallesh.koujalagi@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.