public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
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, 28 May 2026 12:21:59 +1000	[thread overview]
Message-ID: <review-overall-20260527-nova-exports-v2-0-06de4c556d55@nvidia.com> (raw)
In-Reply-To: <20260527-nova-exports-v2-0-06de4c556d55@nvidia.com>

Overall Series Review

Subject: gpu: drm: nova: enable calling into nova-core
Author: Alexandre Courbot <acourbot@nvidia.com>
Patches: 11
Reviewed: 2026-05-28T12:21:59.491666

---

This is a well-structured 7-patch series enabling `nova-drm` to call into `nova-core` as an interim workaround until the Rust build system natively supports cross-crate module dependencies. The approach is pragmatic: export Rust symbols via generated C `EXPORT_SYMBOL_GPL()` calls, generate `.rmeta` metadata for compile-time type resolution, and wire up the Makefile dependencies. The first three patches are preparatory fixes (modpost truncation detection, inlining to shrink symbol names) and the final patch is an explicitly-labeled POC not intended for merge.

**Key concerns:**

1. The modpost fix (patch 1) has a correctness issue with printing `tmp` after truncation — the content is already truncated/partial and may confuse developers.
2. The `#[inline(always)]` patches are reasonable workarounds but scatter hints across core Rust infrastructure to fix a Nova-specific symbol length problem — this should be discussed with the Rust-for-Linux maintainers since it affects all kernel Rust users.
3. The POC patch (7/7) has significant issues with self-referential struct field ordering and `SAFETY` comments that don't fully address the concerns.

Overall, patches 1-6 are in reasonable shape for a stated workaround. Patch 7 needs rework if it were ever to be merged, but it's explicitly labeled as a POC.

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-05-28  2:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 11:52 [PATCH v2 0/7] gpu: drm: nova: enable calling into nova-core Alexandre Courbot
2026-05-27 11:52 ` [PATCH v2 1/7] scripts: modpost: detect and report truncated buf_printf() output Alexandre Courbot
2026-05-27 17:18   ` Nathan Chancellor
2026-05-28  2:21   ` Claude review: " Claude Code Review Bot
2026-05-27 11:52 ` [PATCH v2 2/7] pin_init: always inline the #ident and #project_ident methods Alexandre Courbot
2026-05-27 17:49   ` Gary Guo
2026-05-28  2:22   ` Claude review: " Claude Code Review Bot
2026-05-27 11:52 ` [PATCH v2 3/7] rust: always inline some init methods Alexandre Courbot
2026-05-27 17:54   ` Gary Guo
2026-05-28  2:22   ` Claude review: " Claude Code Review Bot
2026-05-27 11:52 ` [PATCH v2 4/7] gpu: nova-core: export Rust symbols for dependent modules Alexandre Courbot
2026-05-28  2:22   ` Claude review: " Claude Code Review Bot
2026-05-27 11:52 ` [PATCH v2 5/7] gpu: nova-core: emit Rust metadata " Alexandre Courbot
2026-05-28  2:22   ` Claude review: " Claude Code Review Bot
2026-05-27 11:52 ` [PATCH v2 6/7] gpu: drm: nova: build after nova-core metadata Alexandre Courbot
2026-05-28  2:22   ` Claude review: " Claude Code Review Bot
2026-05-27 11:52 ` [PATCH POC v2 7/7] drm: nova: demonstrate interaction with nova-core Alexandre Courbot
2026-05-28  2:22   ` Claude review: " Claude Code Review Bot
2026-05-28  2:21 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-30 14:55 [PATCH 0/7] gpu: drm: nova: enable calling into nova-core 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-20260527-nova-exports-v2-0-06de4c556d55@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