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/vblank: Add some debugging trace events
Date: Fri, 27 Feb 2026 14:40:53 +1000	[thread overview]
Message-ID: <review-patch5-20260224212639.390768-6-sunpeng.li@amd.com> (raw)
In-Reply-To: <20260224212639.390768-6-sunpeng.li@amd.com>

Patch Review

Straightforward tracing additions. Useful for debugging the new deferred path.

**Minor issues:**

1. Format string mismatch in `drm_vblank_get_put_template`:
```c
TP_STRUCT__entry(
    __field(int, refcount)
),
TP_printk(
    "crtc=%d, refcount=%u",    // %u for signed int
```
`refcount` is declared as `int` but printed with `%u`. Use `%d` for consistency.

2. The `drm_vblank_put` trace point reads `atomic_read(&vblank->refcount)` **before** `atomic_dec_and_test()`:
```c
trace_drm_vblank_put(pipe, atomic_read(&vblank->refcount));

/* Last user schedules interrupt disable */
if (!atomic_dec_and_test(&vblank->refcount))
    return;
```
The comment "put's refcount not sync'd using vbl_lock, use for debugging purposes only" is appropriate, but the trace shows the refcount *before* the put, not after. This is fine for debugging but could confuse readers expecting the post-decrement value.

3. The `trace_drm_vblank_get` placement is before the `atomic_add_return`, so it also shows the pre-increment refcount, which is at least consistent with the put trace.

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-02-27  4:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 21:26 [PATCH 0/5] drm/vblank: Deferred Enable and Disable sunpeng.li
2026-02-24 21:26 ` [PATCH 1/5] drm/vblank: Add drm_crtc_vblank_is_off() helper sunpeng.li
2026-02-27  4:40   ` Claude review: " Claude Code Review Bot
2026-02-24 21:26 ` [PATCH 2/5] drm/vblank: Introduce deferred vblank enable/disable sunpeng.li
2026-02-25  4:42   ` kernel test robot
2026-02-27  4:40   ` Claude review: " Claude Code Review Bot
2026-02-24 21:26 ` [PATCH 3/5] drm/amd/display: Refactor amdgpu_dm_crtc_set_vblank sunpeng.li
2026-02-27  4:40   ` Claude review: " Claude Code Review Bot
2026-02-24 21:26 ` [PATCH 4/5] drm/amd/display: Implement deferred vblanks on IPS platforms sunpeng.li
2026-02-27  4:40   ` Claude review: " Claude Code Review Bot
2026-02-24 21:26 ` [PATCH 5/5] drm/vblank: Add some debugging trace events sunpeng.li
2026-02-27  4:40   ` Claude Code Review Bot [this message]
2026-02-27  4:40 ` Claude review: drm/vblank: Deferred Enable and Disable Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-03-23 20:27 [PATCH v2 0/5] " sunpeng.li
2026-03-23 20:27 ` [PATCH v2 5/5] drm/vblank: Add some debugging trace events sunpeng.li
2026-03-24 21:22   ` 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-patch5-20260224212639.390768-6-sunpeng.li@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