From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Introduce cold reset recovery method
Date: Sat, 16 May 2026 13:17:48 +1000 [thread overview]
Message-ID: <review-overall-20260512132614.1793083-7-mallesh.koujalagi@intel.com> (raw)
In-Reply-To: <20260512132614.1793083-7-mallesh.koujalagi@intel.com>
Overall Series Review
Subject: Introduce cold reset recovery method
Author: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
Patches: 12
Reviewed: 2026-05-16T13:17:48.673793
---
This v5 series introduces cold reset recovery for Intel Xe GPUs through the DRM wedge infrastructure. The architecture is: system controller reports hardware errors (PUNIT, memory, compute) via RAS, and when a PUNIT error is detected that persists across warm resets, the driver wedges the device with `DRM_WEDGE_RECOVERY_COLD_RESET`, notifying userspace to power-cycle the slot.
**Patch 1** is a dependency blob from a separate series (explicitly marked "DO NOT REVIEW"), so I'll focus on patches 2-5. The overall design of adding a new recovery method to the DRM wedge framework is straightforward and clean. However, there are several issues ranging from a compile-breaking bug to a duplicate `#define`.
**Key issues:**
1. **Critical bug (Patch 1):** `handle_page_offline()` uses `ret` uninitialized in a `switch` statement — the call that should set it is commented out as a TODO. This is undefined behavior and will be flagged by the compiler.
2. **Duplicate define (Patch 1):** `XE_SYSCTRL_FLOOD` is defined in both `xe_sysctrl_event_types.h` and `xe_sysctrl_mailbox_types.h`.
3. **Patch 5 naming:** Static functions use the `pcie_` prefix which could be confused with PCI core API functions.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-16 3:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 13:26 [PATCH v5 0/5] Introduce cold reset recovery method Mallesh Koujalagi
2026-05-12 13:26 ` [PATCH v5 1/5] Introduce Xe Uncorrectable Error Handling Mallesh Koujalagi
2026-05-16 3:17 ` Claude review: " Claude Code Review Bot
2026-05-12 13:26 ` [PATCH v5 2/5] drm: Add DRM_WEDGE_RECOVERY_COLD_RESET recovery method Mallesh Koujalagi
2026-05-14 7:59 ` Raag Jadav
2026-05-14 9:12 ` Tauro, Riana
2026-05-16 3:17 ` Claude review: " Claude Code Review Bot
2026-05-12 13:26 ` [PATCH v5 3/5] drm/doc: Document " Mallesh Koujalagi
2026-05-14 8:50 ` Raag Jadav
2026-05-16 3:17 ` Claude review: " Claude Code Review Bot
2026-05-12 13:26 ` [PATCH v5 4/5] drm/xe: Handle PUNIT errors by requesting cold-reset recovery Mallesh Koujalagi
2026-05-14 8:13 ` Raag Jadav
2026-05-16 3:17 ` Claude review: " Claude Code Review Bot
2026-05-12 13:26 ` [PATCH v5 5/5] drm/xe: Suppress Surprise Link Down on non-hotplug device Mallesh Koujalagi
2026-05-14 8:35 ` Raag Jadav
2026-05-14 9:36 ` Tauro, Riana
2026-05-16 3:17 ` Claude review: " Claude Code Review Bot
2026-05-16 3:17 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-06 14:23 [PATCH v3 0/4] Introduce cold reset recovery method Mallesh Koujalagi
2026-04-12 4:32 ` Claude review: " Claude Code Review Bot
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=review-overall-20260512132614.1793083-7-mallesh.koujalagi@intel.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox