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: nova-core: gsp: add tests for SplitState
Date: Thu, 19 Feb 2026 18:43:08 +1000	[thread overview]
Message-ID: <review-patch9-20260219-cmdq-continuation-v2-9-2e8b7615536f@nvidia.com> (raw)
In-Reply-To: <20260219-cmdq-continuation-v2-9-2e8b7615536f@nvidia.com>

Patch Review

> +    impl CommandToGsp for TestPayload {
> +        const FUNCTION: MsgFunction = MsgFunction::Nop;
> +        type Command = ();

The tests use `Command = ()` (zero-sized type), which means `MAX_FIRST_PAYLOAD_SIZE == MAX_CMD_SIZE`. This simplifies the boundary testing. It would be nice to also have a test with a non-zero-sized `Command` to exercise the case where `MAX_FIRST_PAYLOAD_SIZE < MAX_CMD_SIZE`, but this is a minor suggestion, not a bug.

> +    fn check_split(t: SplitTest) -> Result {
> +        let payload = TestPayload::new(t.payload_size)?;
> +        let mut state = SplitState::new(&payload)?;
> +
> +        let mut buf = read_payload(&state.command(payload))?;
> +        assert!(buf.len() <= MAX_CMD_SIZE);

The test correctly verifies both the structure (correct number of continuation records, each within the size limit) and the data integrity (reassembled data matches the original pattern). The boundary conditions at `MAX_CMD_SIZE`, `MAX_CMD_SIZE + 1`, `MAX_CMD_SIZE * 2`, and `MAX_CMD_SIZE * 2 + 1` are well-chosen. No issues.

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-02-19  8:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  7:30 [PATCH v2 0/9] gpu: nova-core: gsp: add continuation record support Eliot Courtney
2026-02-19  7:30 ` [PATCH v2 1/9] gpu: nova-core: gsp: sort MsgFunction variants alphabetically Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 2/9] gpu: nova-core: gsp: add mechanism to wait for space on command queue Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 3/9] rust: add EMSGSIZE error code Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 4/9] gpu: nova-core: gsp: add checking oversized commands Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 5/9] gpu: nova-core: gsp: clarify invariant on command queue Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 6/9] gpu: nova-core: gsp: unconditionally call variable payload handling Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 7/9] gpu: nova-core: gsp: add command_size helper Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 8/9] gpu: nova-core: gsp: support large RPCs via continuation record Eliot Courtney
2026-02-19  8:43   ` Claude review: " Claude Code Review Bot
2026-02-19  7:30 ` [PATCH v2 9/9] gpu: nova-core: gsp: add tests for SplitState Eliot Courtney
2026-02-19  8:43   ` Claude Code Review Bot [this message]
2026-02-19  8:43 ` Claude review: gpu: nova-core: gsp: add continuation record support Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-02-26 11:45 [PATCH v3 0/9] " Eliot Courtney
2026-02-26 11:45 ` [PATCH v3 9/9] gpu: nova-core: gsp: add tests for SplitState Eliot Courtney
2026-02-27  2:22   ` 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-patch9-20260219-cmdq-continuation-v2-9-2e8b7615536f@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