Skip to content

Commit 15818b2

Browse files
Jiri Pirkomszyprow
authored andcommitted
dma-buf: heaps: system: document system_cc_shared heap
Document the system_cc_shared dma-buf heap that was introduced recently. Describe its purpose, availability conditions and relation to confidential computing VMs. Signed-off-by: Jiri Pirko <jiri@nvidia.com> Reviewed-by: T.J.Mercier <tjmercier@google.com> Acked-by: Sumit Semwal <sumit.semwal@linaro.org> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Link: https://lore.kernel.org/r/20260407092617.635223-1-jiri@resnulli.us
1 parent 78b30c5 commit 15818b2

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

Documentation/userspace-api/dma-buf-heaps.rst

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,13 @@ following heaps:
1616

1717
- The ``system`` heap allocates virtually contiguous, cacheable, buffers.
1818

19+
- The ``system_cc_shared`` heap allocates virtually contiguous, cacheable,
20+
buffers using shared (decrypted) memory. It is only present on
21+
confidential computing (CoCo) VMs where memory encryption is active
22+
(e.g., AMD SEV, Intel TDX). The allocated pages have the encryption
23+
bit cleared, making them accessible for device DMA without TDISP
24+
support. On non-CoCo VM configurations, this heap is not registered.
25+
1926
- The ``default_cma_region`` heap allocates physically contiguous,
2027
cacheable, buffers. Only present if a CMA region is present. Such a
2128
region is usually created either through the kernel commandline

0 commit comments

Comments
 (0)