drivers/vfio/vfio_iommu_spapr_tce.c

File Facts

System

Linux kernel

Corpus path

drivers/vfio/vfio_iommu_spapr_tce.c

Extension

.c

Size

32786 bytes

Lines

1380

Domain

Driver Families

Bucket

drivers/vfio

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• 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/module.h
• linux/pci.h
• linux/slab.h
• linux/uaccess.h
• linux/err.h
• linux/vfio.h
• linux/vmalloc.h
• linux/sched/mm.h
• linux/sched/signal.h
• linux/mm.h
• vfio.h
• asm/iommu.h
• asm/tce.h
• asm/mmu_context.h

Detected Declarations

• struct tce_iommu_group
• struct tce_iommu_prereg
• struct tce_container
• function tce_iommu_mm_set
• function tce_iommu_prereg_free
• function tce_iommu_unregister_pages
• function list_for_each_entry
• function tce_iommu_register_pages
• function list_for_each_entry
• function tce_page_is_contained
• function tce_groups_attached
• function tce_iommu_find_table
• function tce_iommu_find_free_table
• function tce_iommu_enable
• function tce_iommu_disable
• function tce_iommu_release
• function tce_iommu_unuse_page
• function tce_iommu_prereg_ua_to_hpa
• function tce_iommu_unuse_page_v2
• function tce_iommu_clear
• function tce_iommu_use_page
• function tce_iommu_build
• function tce_iommu_build_v2
• function tce_iommu_create_table
• function tce_iommu_free_table
• function tce_iommu_create_window
• function tce_iommu_remove_window
• function tce_iommu_create_default_window
• function vfio_spapr_ioctl_eeh_pe_op
• function tce_iommu_ioctl
• function list_for_each_entry
• function tce_iommu_release_ownership
• function tce_iommu_take_ownership
• function tce_iommu_attach_group
• function tce_iommu_detach_group
• function list_for_each_entry
• function tce_iommu_init
• function tce_iommu_cleanup
• module init tce_iommu_init

Annotated Snippet

module_init(tce_iommu_init);
module_exit(tce_iommu_cleanup);

MODULE_VERSION(DRIVER_VERSION);
MODULE_LICENSE("GPL v2");
MODULE_AUTHOR(DRIVER_AUTHOR);
MODULE_DESCRIPTION(DRIVER_DESC);

Annotation

• Immediate include surface: `linux/module.h`, `linux/pci.h`, `linux/slab.h`, `linux/uaccess.h`, `linux/err.h`, `linux/vfio.h`, `linux/vmalloc.h`, `linux/sched/mm.h`.
• Detected declarations: `struct tce_iommu_group`, `struct tce_iommu_prereg`, `struct tce_container`, `function tce_iommu_mm_set`, `function tce_iommu_prereg_free`, `function tce_iommu_unregister_pages`, `function list_for_each_entry`, `function tce_iommu_register_pages`, `function list_for_each_entry`, `function tce_page_is_contained`.
• Atlas domain: Driver Families / drivers/vfio.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• 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.