From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/panthor: extend timestamp query with flags
Date: Sun, 22 Mar 2026 04:24:21 +1000 [thread overview]
Message-ID: <review-overall-20260318112952.645160-1-marcin.slusarz@arm.com> (raw)
In-Reply-To: <20260318112952.645160-1-marcin.slusarz@arm.com>
Overall Series Review
Subject: drm/panthor: extend timestamp query with flags
Author: Marcin Slusarz <marcin.slusarz@arm.com>
Patches: 16
Reviewed: 2026-03-22T04:24:21.326403
---
This mbox contains three versions (v1, v2, v3) of the same patch: "drm/panthor: extend timestamp query with flags". The patch extends the `DRM_PANTHOR_DEV_QUERY_TIMESTAMP_INFO` ioctl to support flags that let userspace selectively request GPU timestamps, CPU timestamps (CLOCK_MONOTONIC or CLOCK_MONOTONIC_RAW), GPU cycle counts, and query duration measurement. The motivation is to improve `VK_KHR_calibrated_timestamps` support. I'll focus the detailed review on **v3** as the latest version, with notes on the evolution.
The overall approach is reasonable — extending an existing query struct with flags and new fields while maintaining backward compatibility. However, there are several concerns around the UAPI design, the `timens_add_monotonic` usage with interrupts disabled, and the `copy_struct_from_user` interaction with panthor's existing UOBJ infrastructure.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-21 18:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 11:29 [PATCH] drm/panthor: extend timestamp query with flags Marcin Slusarz
2026-03-18 12:10 ` Boris Brezillon
2026-03-18 14:51 ` Marcin Ślusarz
2026-03-18 15:20 ` Steven Price
2026-03-18 16:06 ` Boris Brezillon
2026-03-18 16:27 ` Marcin Ślusarz
2026-03-18 16:37 ` Boris Brezillon
2026-03-18 16:34 ` Boris Brezillon
2026-03-24 20:49 ` Claude review: " Claude Code Review Bot
2026-03-21 18:32 ` Claude Code Review Bot
2026-03-21 18:32 ` Claude Code Review Bot
2026-03-19 8:25 ` [PATCH v2] " Marcin Slusarz
2026-03-19 10:15 ` Boris Brezillon
2026-03-19 11:00 ` [PATCH v3] " Marcin Slusarz
2026-03-19 11:10 ` Boris Brezillon
2026-03-19 11:43 ` Liviu Dudau
2026-03-19 12:39 ` Marcin Ślusarz
2026-03-19 15:17 ` Liviu Dudau
2026-03-19 15:33 ` Marcin Ślusarz
2026-03-23 13:16 ` Liviu Dudau
2026-03-23 16:12 ` Marcin Ślusarz
2026-03-24 10:41 ` Liviu Dudau
2026-03-24 13:26 ` Marcin Ślusarz
2026-03-21 18:24 ` Claude Code Review Bot [this message]
2026-03-21 18:32 ` Claude review: " Claude Code Review Bot
2026-03-24 13:25 ` [PATCH v4] " Marcin Slusarz
2026-03-24 15:25 ` Liviu Dudau
2026-03-24 16:05 ` Liviu Dudau
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-20260318112952.645160-1-marcin.slusarz@arm.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