From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: dma-buf: heaps: system: document system_cc_shared heap
Date: Sun, 12 Apr 2026 13:56:44 +1000 [thread overview]
Message-ID: <review-patch1-20260407092617.635223-1-jiri@resnulli.us> (raw)
In-Reply-To: <20260407092617.635223-1-jiri@resnulli.us>
Patch Review
**Placement**: Correct -- the new entry is inserted between the `system` heap and the `default_cma_region` heap, which is the natural ordering since `system_cc_shared` is a variant of the system heap.
**Content accuracy**: The description covers the key aspects:
- What it allocates (virtually contiguous, cacheable, shared/decrypted memory)
- When it's present (CoCo VMs with memory encryption active)
- Why it exists (device DMA without TDISP support)
- When it's absent (non-CoCo configurations)
**Minor wording nit**: The phrase:
```
making them accessible for device DMA without TDISP
support
```
is slightly ambiguous -- it could be parsed as "accessible for [device DMA without TDISP support]" or "accessible for device DMA, [without needing TDISP support]". Both readings arrive at the same meaning, but adding a comma would make it unambiguous:
```
making them accessible for device DMA, without requiring TDISP support.
```
This is a very minor readability suggestion, not a blocking issue.
**Naming convention**: The name `system_cc_shared` aligns well with the naming convention guidelines documented later in the same file -- it describes the memory properties (shared/decrypted for confidential computing) rather than implementation details.
**Reviewed-by**: Already has `Reviewed-by: T.J.Mercier <tjmercier@google.com>`.
**Overall**: Clean documentation patch. No objections.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-04-12 3:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 9:26 [PATCH v2] dma-buf: heaps: system: document system_cc_shared heap Jiri Pirko
2026-04-10 12:14 ` Sumit Semwal
2026-04-10 12:20 ` Marek Szyprowski
2026-04-12 3:56 ` Claude review: " Claude Code Review Bot
2026-04-12 3:56 ` Claude Code Review Bot [this message]
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-20260407092617.635223-1-jiri@resnulli.us \
--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