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: drm/nouveau: nv04 FIFO cleanup + recovery for Tesla
Date: Sat, 16 May 2026 11:34:49 +1000	[thread overview]
Message-ID: <review-overall-20260513175014.96599-1-marek@czernohous.de> (raw)
In-Reply-To: <20260513175014.96599-1-marek@czernohous.de>

Overall Series Review

Subject: drm/nouveau: nv04 FIFO cleanup + recovery for Tesla
Author: Marek Czernohous <mczernohous@gmail.com>
Patches: 3
Reviewed: 2026-05-16T11:34:49.332858

---

This is a well-structured two-patch series adding observability and recovery to the legacy nv04 FIFO path on Tesla GPUs. The cover letter is thorough, the design (Tier-1 channel-kill + Tier-2 sliding-window wedge) is sound, and the code follows existing nouveau patterns (e.g., the `nvkm_chan_get_chid` / `nvkm_chan_error` / `nvkm_chan_put` sequence mirrors Fermi+ paths in gf100.c, ga100.c, gv100.c).

The series is relatively clean. The main issues are:

1. **German comments in the public header** — the `struct nvkm_fifo_wedge` field comments are in German. Kernel code should use English.
2. **No unwedge/reset mechanism** — once `atomic_xchg(&w->wedged, 1)` fires, Tier-2 is permanently disabled for the lifetime of the driver. This is a design point worth an explicit note or a deliberate decision to document.
3. **Wedge init/fini runs for all GPU generations** — `nv04_fifo_wedge_init`/`fini` is called unconditionally from `nvkm_fifo_new_`/`nvkm_fifo_dtor`, even though `nv04_fifo_recover` is only called from the nv04 FIFO interrupt handler. Harmless but slightly untidy.

No blocking issues found. The locking is correct, `schedule_work` from IRQ context is fine, and the workqueue indirection for `drm_dev_wedged_event` (which may sleep via `kobject_uevent_env`) is the right approach.

---

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-05-16  1:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 17:50 [PATCH 0/2] drm/nouveau: nv04 FIFO cleanup + recovery for Tesla Marek Czernohous
2026-05-13 17:50 ` [PATCH 1/2] drm/nouveau/fifo/nv04: filter benign CACHE_ERROR from Mesa NV50 bind probe Marek Czernohous
2026-05-16  1:34   ` Claude review: " Claude Code Review Bot
2026-05-13 17:50 ` [PATCH 2/2] drm/nouveau/fifo: add recovery path for Tesla cache_error/dma_pusher Marek Czernohous
2026-05-16  1:34   ` Claude review: " Claude Code Review Bot
2026-05-16  1:34 ` 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-20260513175014.96599-1-marek@czernohous.de \
    --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