From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/atomic: introduce PAGE_FLIP_EVENT property
Date: Thu, 04 Jun 2026 15:29:59 +1000 [thread overview]
Message-ID: <review-overall-20260530171422.4615-1-contact@emersion.fr> (raw)
In-Reply-To: <20260530171422.4615-1-contact@emersion.fr>
Overall Series Review
Subject: drm/atomic: introduce PAGE_FLIP_EVENT property
Author: Simon Ser <contact@emersion.fr>
Patches: 3
Reviewed: 2026-06-04T15:29:59.502018
---
This is a single patch from Simon Ser that introduces a new `PAGE_FLIP_EVENT` atomic CRTC property, allowing userspace to request page-flip events on a per-CRTC basis rather than the current all-or-nothing `DRM_MODE_PAGE_FLIP_EVENT` flag. The motivation is well-explained and addresses real pain points in compositors (gamescope, libliftoff, wlroots).
The approach is sound and follows established patterns (modeled after `OUT_FENCE_PTR` — always reads as zero, write-only semantic). The implementation is compact and mostly correct, but there is one significant bug around state duplication/reset and a few smaller issues worth discussing.
**Key concern:** The new `page_flip_event_requested` field in `drm_crtc_state` is not cleared in `__drm_atomic_helper_crtc_duplicate_state()`, which means it could carry over from a previous committed state if the memcpy copies a stale `true` value. This is unlike `event`, `async_flip`, and other per-commit fields that are explicitly cleared there.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 17:14 [PATCH] drm/atomic: introduce PAGE_FLIP_EVENT property Simon Ser
2026-05-31 9:10 ` Xaver Hugl
2026-05-31 9:26 ` Simon Ser
2026-06-04 5:29 ` Claude Code Review Bot [this message]
2026-06-04 5:29 ` 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-20260530171422.4615-1-contact@emersion.fr \
--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