From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: gpu: drm: nova: enable calling into nova-core
Date: Thu, 04 Jun 2026 16:23:29 +1000 [thread overview]
Message-ID: <review-overall-20260530-nova-exports-v3-0-1202aa339ef7@nvidia.com> (raw)
In-Reply-To: <20260530-nova-exports-v3-0-1202aa339ef7@nvidia.com>
Overall Series Review
Subject: gpu: drm: nova: enable calling into nova-core
Author: Alexandre Courbot <acourbot@nvidia.com>
Patches: 11
Reviewed: 2026-06-04T16:23:29.159435
---
This is a 5-patch series from Alexandre Courbot (NVIDIA) that enables `nova-drm` to call into `nova-core` by working around the current lack of native Rust cross-crate module dependency support in the kernel build system. The approach has three parts: (1) inline some Rust init methods to avoid excessively long symbol names, (2) export nova-core's Rust symbols via a generated C file with `EXPORT_SYMBOL_GPL()`, and (3) emit Rust `.rmeta` metadata so nova-drm can resolve nova-core's types at compile time.
**Strengths:**
- Well-documented as a temporary workaround with clear rationale
- The `#[inline]` patch (1/5) has standalone merit beyond the workaround
- Build system integration is thoughtful (private directory to avoid parallel build races, order-only dependencies, `filechk` for generated headers)
- Patch 5 is honestly labeled as POC/not-for-merge
**Concerns:**
- Patch 2 exports ALL Rust text symbols from nova-core, which is far more than nova-drm needs — this leaks internal API surface via `EXPORT_SYMBOL_GPL()`
- Patch 3 effectively compiles nova-core twice (once for the .o, once for the .rmeta), increasing build time
- The patches are based on `drm-rust-next` which has diverged significantly from the `drm-next` tree (the whole `'bound` lifetime / HRT v5 infrastructure), so they could not be verified against the reference tree
**Overall: The series is a reasonable pragmatic workaround. Patches 1-4 look correct for their stated purpose. The POC patch 5 demonstrates sound design for the inter-module data flow but has some rough edges typical of demo code.**
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 6:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 15:27 [PATCH v3 0/5] gpu: drm: nova: enable calling into nova-core Alexandre Courbot
2026-05-29 15:27 ` [PATCH v3 1/5] rust: inline some init methods Alexandre Courbot
2026-06-03 11:52 ` Gary Guo
2026-06-04 6:23 ` Claude review: " Claude Code Review Bot
2026-05-29 15:27 ` [PATCH v3 2/5] gpu: nova-core: export Rust symbols for dependent modules Alexandre Courbot
2026-06-04 6:23 ` Claude review: " Claude Code Review Bot
2026-05-29 15:27 ` [PATCH v3 3/5] gpu: nova-core: emit Rust metadata " Alexandre Courbot
2026-06-04 6:23 ` Claude review: " Claude Code Review Bot
2026-05-29 15:27 ` [PATCH v3 4/5] gpu: drm: nova: build after nova-core metadata Alexandre Courbot
2026-06-04 6:23 ` Claude review: " Claude Code Review Bot
2026-05-29 15:27 ` [PATCH POC v3 5/5] drm: nova: demonstrate interaction with nova-core Alexandre Courbot
2026-06-04 6:23 ` Claude review: " Claude Code Review Bot
2026-06-01 13:50 ` [PATCH v3 0/5] gpu: drm: nova: enable calling into nova-core Miguel Ojeda
2026-06-01 17:00 ` Miguel Ojeda
2026-06-03 10:30 ` Alexandre Courbot
2026-06-03 11:49 ` Miguel Ojeda
2026-06-04 6:23 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 11:52 [PATCH v2 0/7] " Alexandre Courbot
2026-05-28 2:21 ` Claude review: " Claude Code Review Bot
2026-04-30 14:55 [PATCH 0/7] " Alexandre Courbot
2026-05-05 0:17 ` 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-20260530-nova-exports-v3-0-1202aa339ef7@nvidia.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