From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: gpu: nova-core: emit Rust metadata for dependent modules
Date: Thu, 04 Jun 2026 16:23:29 +1000 [thread overview]
Message-ID: <review-patch3-20260530-nova-exports-v3-3-1202aa339ef7@nvidia.com> (raw)
In-Reply-To: <20260530-nova-exports-v3-3-1202aa339ef7@nvidia.com>
Patch Review
**Status: Looks good**
This adds Makefile rules to produce `libnova_core.rmeta` so dependent Rust modules can use `--extern nova_core=<path>` for compile-time type resolution.
The build is isolated in `.nova_core_rmeta/` to avoid racing with the main `nova_core.o` compilation on rustc's intermediate file names — this is a real problem since rustc writes intermediate objects with deterministic names. The implementation:
```makefile
cmd_rustc_rmeta_rs = mkdir -p $(dir $@); \
$(rust_common_cmd) --emit=metadata=$@ \
--emit=obj=$(basename $@).o $<; \
rm -f $(basename $@).o
```
The `--emit=obj=...` followed by `rm -f` is necessary because some rustc versions require code generation to produce correct metadata. The discarded `.o` is placed in the private directory so it doesn't collide.
The two-step approach (private build → `if_changed,copy` to stable path) ensures consumers see a stable path and the copy only happens when content changes. The `private __modname`, `part-of-builtin`, and `part-of-module` settings correctly replicate the build context.
The downside is compiling nova-core effectively twice (once for .o, once for .rmeta), but this is acceptable for a temporary workaround.
---
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 Code Review Bot [this message]
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 review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-05-27 11:52 [PATCH v2 0/7] " Alexandre Courbot
2026-05-27 11:52 ` [PATCH v2 5/7] gpu: nova-core: emit Rust metadata for dependent modules Alexandre Courbot
2026-05-28 2:22 ` Claude review: " Claude Code Review Bot
2026-04-30 14:55 [PATCH 0/7] gpu: drm: nova: enable calling into nova-core Alexandre Courbot
2026-04-30 14:55 ` [PATCH 5/7] gpu: nova-core: emit Rust metadata for dependent modules 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-patch3-20260530-nova-exports-v3-3-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