From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: accel/amdxdna: Support retrieving hardware context debug information
Date: Sat, 14 Mar 2026 06:42:17 +1000 [thread overview]
Message-ID: <review-overall-20260313181413.1108841-1-lizhi.hou@amd.com> (raw)
In-Reply-To: <20260313181413.1108841-1-lizhi.hou@amd.com>
Overall Series Review
Subject: accel/amdxdna: Support retrieving hardware context debug information
Author: Lizhi Hou <lizhi.hou@amd.com>
Patches: 3
Reviewed: 2026-03-14T06:42:17.931971
---
This is a single patch adding support for retrieving hardware context health/debug information from the AIE2 firmware in the amdxdna accelerator driver. When a command times out, the driver queries the firmware for diagnostic information (GET_APP_HEALTH) and makes it available both via kernel log messages and through the hardware context query IOCTL to userspace.
The patch is generally well-structured and follows existing driver patterns. However, there are several issues that should be addressed, ranging from a potential stack overflow to a missing cache invalidation and some behavioral concerns.
**Key concerns:**
1. Large stack allocation (~560 bytes) in an IOCTL callback path
2. Missing DMA sync/cache invalidation after device write
3. Firmware query in a per-context iteration loop could cause latency issues under `dev_lock`
4. Minor: passing non-zero size with potentially NULL data pointer
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-13 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 18:14 [PATCH V1] accel/amdxdna: Support retrieving hardware context debug information Lizhi Hou
2026-03-13 18:30 ` Mario Limonciello
2026-03-13 20:26 ` Lizhi Hou
2026-03-13 20:42 ` Claude Code Review Bot [this message]
2026-03-13 20:42 ` 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-20260313181413.1108841-1-lizhi.hou@amd.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