drivers/dma-buf/dma-resv.c

File Facts

System

Linux kernel

Corpus path

drivers/dma-buf/dma-resv.c

Extension

.c

Size

22883 bytes

Lines

819

Domain

Driver Families

Bucket

drivers/dma-buf

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/dma-resv.h
• linux/dma-fence-array.h
• linux/export.h
• linux/mm.h
• linux/sched/mm.h
• linux/mmu_notifier.h
• linux/seq_file.h

Detected Declarations

• struct dma_resv_list
• function dma_resv_list_entry
• function dma_resv_list_set
• function dma_resv_list_free
• function dma_resv_init
• function dma_resv_fini
• function dma_resv_add_fence
• function dma_resv_reserve_fences
• function dma_resv_reserve_fences
• function dma_resv_replace_fences
• function dma_resv_iter_restart_unlocked
• function dma_resv_iter_walk_unlocked
• function dma_resv_iter_next_unlocked
• function dma_resv_iter_is_restarted
• function dma_resv_iter_next_unlocked
• function dma_resv_copy_fences
• function dma_resv_get_fences
• function dma_resv_get_singleton
• function dma_resv_lock
• function dma_resv_set_deadline
• function dma_resv_lock
• function dma_resv_describe
• function dma_resv_for_each_fence
• function dma_resv_lockdep
• module init dma_resv_lockdep
• export reservation_ww_class
• export dma_resv_init
• export dma_resv_fini
• export dma_resv_reserve_fences
• export dma_resv_reset_max_fences
• export dma_resv_add_fence
• export dma_resv_replace_fences
• export dma_resv_iter_first_unlocked
• export dma_resv_iter_next_unlocked
• export dma_resv_iter_first
• export dma_resv_iter_next
• export dma_resv_copy_fences
• export dma_resv_get_fences
• export dma_resv_get_singleton
• export dma_resv_wait_timeout
• export dma_resv_set_deadline
• export dma_resv_test_signaled
• export dma_resv_describe

Annotated Snippet

subsys_initcall(dma_resv_lockdep);
#endif

Annotation

• Immediate include surface: `linux/dma-resv.h`, `linux/dma-fence-array.h`, `linux/export.h`, `linux/mm.h`, `linux/sched/mm.h`, `linux/mmu_notifier.h`, `linux/seq_file.h`.
• Detected declarations: `struct dma_resv_list`, `function dma_resv_list_entry`, `function dma_resv_list_set`, `function dma_resv_list_free`, `function dma_resv_init`, `function dma_resv_fini`, `function dma_resv_add_fence`, `function dma_resv_reserve_fences`, `function dma_resv_reserve_fences`, `function dma_resv_replace_fences`.
• Atlas domain: Driver Families / drivers/dma-buf.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.