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: Limit DRM_IOCTL_WAIT_VBLANK to vblank interrupts
Date: Thu, 28 May 2026 12:19:14 +1000	[thread overview]
Message-ID: <review-overall-20260527133917.207150-1-tzimmermann@suse.de> (raw)
In-Reply-To: <20260527133917.207150-1-tzimmermann@suse.de>

Overall Series Review

Subject: drm: Limit DRM_IOCTL_WAIT_VBLANK to vblank interrupts
Author: Thomas Zimmermann <tzimmermann@suse.de>
Patches: 11
Reviewed: 2026-05-28T12:19:14.368165

---

This is a well-structured 9-patch series from Thomas Zimmermann that addresses a real semantic problem: `DRM_IOCTL_WAIT_VBLANK` (and the newer `CRTC_GET_SEQUENCE`/`CRTC_QUEUE_SEQUENCE` ioctls) being available on devices that only have software-simulated vblank timers (no hardware vblank interrupt). For such devices, waiting for vblank is meaningless since the timer is not synchronized to any display refresh.

The approach is clean: patch 1 renames the init function to `drmm_vblank_init()` with a flags parameter, patch 2 adds the `DRM_VBLANK_FLAG_SIMULATED` flag and the ioctl filtering, and patches 3-9 convert the known simulated-vblank drivers. The series is logically ordered and easy to bisect.

**Overall: looks good.** A few minor observations below, none blocking.

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-05-28  2:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 13:32 [PATCH v2 0/9] drm: Limit DRM_IOCTL_WAIT_VBLANK to vblank interrupts Thomas Zimmermann
2026-05-27 13:32 ` [PATCH v2 1/9] drm/vblank: Add drmm_vblank_init() to indicate managed cleanup Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 2/9] drm/vblank: Add DRM_VBLANK_FLAG_SIMULATED Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 3/9] drm/amdgpu: vkms: Set DRM_VBLANK_FLAG_SIMULATED Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 4/9] drm/bochs: " Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 5/9] drm/cirrus: " Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 6/9] drm/hypervdrm: " Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 7/9] drm/qxl: " Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 8/9] drm/virtgpu: " Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 13:32 ` [PATCH v2 9/9] drm/vkms: " Thomas Zimmermann
2026-05-28  2:19   ` Claude review: " Claude Code Review Bot
2026-05-27 16:31 ` [PATCH v2 0/9] drm: Limit DRM_IOCTL_WAIT_VBLANK to vblank interrupts Julian Orth
2026-05-28  2:19 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-15 11:55 [PATCH " Thomas Zimmermann
2026-05-15 23:20 ` 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-20260527133917.207150-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