From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm: Remove DRIVER_GEM_GPUVA feature flag
Date: Thu, 23 Apr 2026 08:39:45 +1000 [thread overview]
Message-ID: <review-patch1-20260421084701.24227-1-laura.nao@collabora.com> (raw)
In-Reply-To: <20260421084701.24227-1-laura.nao@collabora.com>
Patch Review
**Core DRM changes (drm_gem.c, drm_drv.h, drm_gem.h, drm_debugfs.h):**
These are correct. The key observations:
1. `drm_gem_gpuva_init()` is just `INIT_LIST_HEAD(&obj->gpuva.list)` — calling it unconditionally for every GEM object is harmless. The `mutex_init(&obj->gpuva.lock)` at line 230 of `drm_gem.c` is already unconditional, so the list head init is the only thing that was gated.
2. The `DRM_DEBUGFS_GPUVA_INFO` change from `DRIVER_GEM_GPUVA` to `0` is correct. Looking at `drm_debugfs_create_files()`:
```c
if (features && !drm_core_check_all_features(dev, features))
continue;
```
Passing `0` means `features` is falsy, so the condition short-circuits and the entry is always created — but only for drivers that actually use `DRM_DEBUGFS_GPUVA_INFO` in their debugfs info list (panthor and nouveau). Non-GPUVA drivers never reference this macro, so they don't get a spurious "gpuvas" debugfs entry. This is fine.
3. Removing the enum value and doc comment from `drm_drv.h` is clean. Note that `BIT(8)` is left as a gap — this is normal for DRM driver feature flags and avoids ABI issues with out-of-tree drivers.
4. The doc update in `drm_gem.h` removing the "only necessary for drivers intending to support DRIVER_GEM_GPUVA" comment is appropriate.
**Driver changes (pvr_drv.c, msm_drv.c, nouveau_drm.c, panthor_drv.c, xe_device.c):**
All driver removals of the flag from `.driver_features` look correct and mechanical.
**One point to note — nouveau double-init:**
In `nouveau_bo.c:394`, nouveau has an explicit call:
```c
drm_gem_gpuva_init(&nvbo->bo.base);
```
This exists because nouveau needs the list initialized *before* `ttm_bo_init_reserved()` (as the comment explains: "Subsequent bo_move() callbacks might already iterate the GEMs GPUVA list"). Previously, the core's `drm_gem_private_object_init()` would also call it (gated by the feature flag). With this patch, the core now calls it unconditionally, and then nouveau calls it again. Since it's just `INIT_LIST_HEAD()`, double-calling is harmless (re-initializing an empty list head is a no-op in effect). However, it would be tidier to also remove the now-redundant explicit call in `nouveau_bo.c` and its associated comment. This is a minor cleanup opportunity, not a correctness issue — but it would make the patch more complete.
**Summary:** The patch is correct and well-reasoned. The only suggestion is optionally removing the now-redundant `drm_gem_gpuva_init()` call in `drivers/gpu/drm/nouveau/nouveau_bo.c:394` (and its comment block at lines 391-393), since the core will now always handle this initialization.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-22 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 8:47 [PATCH] drm: Remove DRIVER_GEM_GPUVA feature flag Laura Nao
2026-04-21 13:01 ` Thomas Hellström
2026-04-21 15:32 ` Liviu Dudau
2026-04-21 16:34 ` Rob Clark
2026-04-22 22:39 ` Claude Code Review Bot [this message]
2026-04-22 22:39 ` 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-patch1-20260421084701.24227-1-laura.nao@collabora.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