public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Introduce cold reset recovery method
Date: Sun, 12 Apr 2026 14:32:33 +1000	[thread overview]
Message-ID: <review-overall-20260406142325.157035-6-mallesh.koujalagi@intel.com> (raw)
In-Reply-To: <20260406142325.157035-6-mallesh.koujalagi@intel.com>

Overall Series Review

Subject: Introduce cold reset recovery method
Author: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
Patches: 8
Reviewed: 2026-04-12T14:32:33.157016

---

This v3 series adds cold-reset recovery support for the Xe driver, building on top of an unmerged RAS/PCI-error-handling infrastructure series ([PATCH] "Introduce Xe Uncorrectable Error Handling"). The series introduces `DRM_WEDGE_RECOVERY_COLD_RESET` at the DRM core level and wires it up for PUNIT errors in the Xe driver.

**Key concerns:**

1. **Patch 1 is marked "DO NOT REVIEW" but carries significant architectural decisions** that directly affect the reviewability of patches 2-4. The PCI error recovery path in `xe_pci_error_slot_reset()` has serious issues (calling `pdev->driver->remove()`/`probe()` directly, using `devres_release_group()` in a fragile way) that affect the entire series. The dependency chain also means the `xe_sysctrl_mailbox` infrastructure (`has_sysctrl`, `xe_sysctrl_send_command`, etc.) doesn't exist in drm-next, making it impossible to verify compilation or correctness.

2. **The `in_recovery` atomic overlaps with the `wedged.flag` atomic** in unclear ways. Both serve to block operations during error states, but the interaction and lifecycle differences are not well documented.

3. **The cold-reset recovery script in the documentation is incomplete** — it only handles the slot-power-cycle case and does nothing meaningful when no slot is found (just prints "No slot found" and exits).

---

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-04-12  4:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 14:23 [PATCH v3 0/4] Introduce cold reset recovery method Mallesh Koujalagi
2026-04-06 14:23 ` [PATCH v3 1/4] Introduce Xe Uncorrectable Error Handling Mallesh Koujalagi
2026-04-12  4:32   ` Claude review: " Claude Code Review Bot
2026-04-06 14:23 ` [PATCH v3 2/4] drm: Add DRM_WEDGE_RECOVERY_COLD_RESET recovery method Mallesh Koujalagi
2026-04-08  7:46   ` Raag Jadav
2026-04-12  4:32   ` Claude review: " Claude Code Review Bot
2026-04-06 14:23 ` [PATCH v3 3/4] drm/doc: Document " Mallesh Koujalagi
2026-04-08  8:01   ` Raag Jadav
2026-04-12  4:32   ` Claude review: " Claude Code Review Bot
2026-04-06 14:23 ` [PATCH v3 4/4] drm/xe: Handle PUNIT errors by requesting cold-reset recovery Mallesh Koujalagi
2026-04-08  8:09   ` Raag Jadav
2026-04-12  4:32   ` Claude review: " Claude Code Review Bot
2026-04-12  4:32 ` Claude Code Review Bot [this message]

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-20260406142325.157035-6-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