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: accel/amdxdna: Read real-time clock frequencies
Date: Sun, 12 Apr 2026 14:21:09 +1000	[thread overview]
Message-ID: <review-overall-20260406220526.4027917-1-lizhi.hou@amd.com> (raw)
In-Reply-To: <20260406220526.4027917-1-lizhi.hou@amd.com>

Overall Series Review

Subject: accel/amdxdna: Read real-time clock frequencies
Author: Lizhi Hou <lizhi.hou@amd.com>
Patches: 2
Reviewed: 2026-04-12T14:21:09.757535

---

This is a single patch that bundles two logically distinct changes:

1. **Refactoring `hw_ops` from an embedded struct to a const pointer** — enabling sharing of the ops struct across NPU generations and making `npu4_set_dpm` static.
2. **Adding a new `update_counters` callback** that reads real-time clock frequencies from the AMD PMF (Platform Management Framework) interface.

The refactoring is clean and well-motivated: npu5 and npu6 already reused `npu4_set_dpm`, so sharing a single `npu4_hw_ops` const struct is the right consolidation. However, kernel convention strongly favors splitting these into at least two patches (refactor first, new feature second) for easier bisection and review.

The core concern is the **field name mapping** in `npu4_update_counters` between PMF metrics fields and driver fields, which is confusing and needs explicit justification. There are also issues around silent error suppression and a missing `max_tops` update in the new callback.

**Overall: Needs revision.** The approach is sound but the naming confusion warrants clarification, the error handling in the macro should be addressed, and the patch should ideally be split.

---

---
Generated by Claude Code Patch Reviewer

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-06 22:05 [PATCH V1] accel/amdxdna: Read real-time clock frequencies Lizhi Hou
2026-04-11  3:33 ` Mario Limonciello
2026-04-12  4:21 ` Claude Code Review Bot [this message]
2026-04-12  4:21 ` 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-20260406220526.4027917-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