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: timer: Fix timestamps and improve reliabilty
Date: Thu, 04 Jun 2026 14:03:58 +1000	[thread overview]
Message-ID: <review-overall-20260601141922.91498-1-tzimmermann@suse.de> (raw)
In-Reply-To: <20260601141922.91498-1-tzimmermann@suse.de>

Overall Series Review

Subject: drm/vblank: timer: Fix timestamps and improve reliabilty
Author: Thomas Zimmermann <tzimmermann@suse.de>
Patches: 11
Reviewed: 2026-06-04T14:03:58.367915

---

This series fixes timestamps and improves reliability for the DRM vblank timer infrastructure, used by virtual/software GPU drivers (vkms, bochs, virtio, vmwgfx). The intent is sound — the timestamp calculation has long-standing issues, and the improvements are worthwhile.

However, **Patch 3 introduces a clock domain mismatch bug** that affects multiple subsequent patches. The timer is switched to `CLOCK_BOOTTIME`, but the initial timer start and various timestamp reads/comparisons still use `ktime_get()` / `ktime_get_ns()` which return `CLOCK_MONOTONIC` time. On any system that has been suspended, boottime and monotonic time diverge, making the comparisons invalid. This is the most critical issue in the series.

Additionally, **Patch 1 does not update the vmwgfx caller** (`vmw_vkms_get_vblank_timestamp`), which still ignores the new return value and will return `true` with stale/uninitialized `vblank_time` on error.

The refactoring patches (4, 7) are reasonable, and Patch 6 is a correct and clear bugfix. Patch 2's timestamp correction logic is sound in principle.

---

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-06-04  4:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01 14:08 [PATCH 0/7] drm/vblank: timer: Fix timestamps and improve reliabilty Thomas Zimmermann
2026-06-01 14:08 ` [PATCH 1/7] drm/vblank: timer: Return success status from get_vblank_timeout Thomas Zimmermann
2026-06-04  4:03   ` Claude review: " Claude Code Review Bot
2026-06-01 14:08 ` [PATCH 2/7] drm/vblank: timer: Fix timestamp calculation Thomas Zimmermann
2026-06-01 16:24   ` Michel Dänzer
2026-06-01 17:30     ` Thomas Zimmermann
2026-06-02 14:14       ` Michel Dänzer
2026-06-04  4:03   ` Claude review: " Claude Code Review Bot
2026-06-01 14:08 ` [PATCH 3/7] drm/vblank: timer: Use absolute timer since boot Thomas Zimmermann
2026-06-04  4:03   ` Claude review: " Claude Code Review Bot
2026-06-01 14:08 ` [PATCH 4/7] drm/vblank: timer: Reorganize get_vblank_timeout Thomas Zimmermann
2026-06-04  4:03   ` Claude review: " Claude Code Review Bot
2026-06-01 14:08 ` [PATCH 5/7] drm/vblank: timer: Estimate vblank timeout if timer is disabled Thomas Zimmermann
2026-06-04  4:03   ` Claude review: " Claude Code Review Bot
2026-06-01 14:08 ` [PATCH 6/7] drm/vblank: timer: Verify that expiry time is in the future Thomas Zimmermann
2026-06-04  4:03   ` Claude review: " Claude Code Review Bot
2026-06-01 14:08 ` [PATCH 7/7] drm/vblank: timer: Avoid reading the vblank time unnecessarily Thomas Zimmermann
2026-06-04  4:04   ` Claude review: " Claude Code Review Bot
2026-06-04  4:03 ` 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-20260601141922.91498-1-tzimmermann@suse.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