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: Mon, 25 May 2026 21:57:08 +1000	[thread overview]
Message-ID: <review-overall-20260520113351.171119-7-mallesh.koujalagi@intel.com> (raw)
In-Reply-To: <20260520113351.171119-7-mallesh.koujalagi@intel.com>

Overall Series Review

Subject: Introduce cold reset recovery method
Author: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
Patches: 6
Reviewed: 2026-05-25T21:57:08.799531

---

This v6 series adds a `DRM_WEDGE_RECOVERY_COLD_RESET` recovery method for Intel Xe GPUs, targeting PUNIT errors that persist across warm resets and require a full slot power cycle. The design is sound: detect the error via RAS infrastructure, wedge the device, emit a uevent, and let userspace perform the power cycle.

The DRM core change (patch 2) is clean and minimal. The documentation (patch 3) is well-written with a practical example script. The PUNIT handler (patch 4) correctly uses the wedge API. The AER SLD suppression (patch 5) is architecturally sensible but has a concern about the mask never being restored on failure.

Patch 1 is marked "DO NOT REVIEW - COMPILATION ONLY" but has a clear uninitialized variable bug and a wedge API bypass that could trigger an assertion, which I flag below for completeness since it ships as part of this build.

**Key concerns:**
- Uninitialized variable in `handle_page_offline()` (patch 1)
- `xe_pci_error_handling()` bypasses `xe_device_declare_wedged()` and could hit the `xe_gt_assert` if `wedged.mode == XE_WEDGED_MODE_NEVER` (patch 1)
- Duplicate `XE_SYSCTRL_FLOOD` macro definition across two headers (patch 1)
- SLD mask in patch 5 is never restored if cold reset fails or is never performed

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-05-25 11:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 11:33 [PATCH v6 0/5] Introduce cold reset recovery method Mallesh Koujalagi
2026-05-20 11:33 ` [PATCH v6 1/5] Introduce Xe Uncorrectable Error Handling Mallesh Koujalagi
2026-05-25 11:57   ` Claude review: " Claude Code Review Bot
2026-05-20 11:33 ` [PATCH v6 2/5] drm: Add DRM_WEDGE_RECOVERY_COLD_RESET recovery method Mallesh Koujalagi
2026-05-25 11:57   ` Claude review: " Claude Code Review Bot
2026-05-20 11:33 ` [PATCH v6 3/5] drm/doc: Document " Mallesh Koujalagi
2026-05-25 11:57   ` Claude review: " Claude Code Review Bot
2026-05-20 11:33 ` [PATCH v6 4/5] drm/xe: Handle PUNIT errors by requesting cold-reset recovery Mallesh Koujalagi
2026-05-25 11:57   ` Claude review: " Claude Code Review Bot
2026-05-20 11:33 ` [PATCH v6 5/5] drm/xe: Suppress Surprise Link Down on non-hotplug device Mallesh Koujalagi
2026-05-25 11:57   ` Claude review: " Claude Code Review Bot
2026-05-25 11:57 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-12 13:26 [PATCH v5 0/5] Introduce cold reset recovery method Mallesh Koujalagi
2026-05-16  3:17 ` Claude review: " Claude Code Review Bot
2026-04-06 14:23 [PATCH v3 0/4] " 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-20260520113351.171119-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