drivers/virtio/virtio_mmio.c

File Facts

System

Linux kernel

Corpus path

drivers/virtio/virtio_mmio.c

Extension

.c

Size

20963 bytes

Lines

830

Domain

Driver Families

Bucket

drivers/virtio

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 IRQ or DMA behavior; this matters for the representative real-device path.
• 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/acpi.h
• linux/dma-mapping.h
• linux/highmem.h
• linux/interrupt.h
• linux/io.h
• linux/list.h
• linux/module.h
• linux/of.h
• linux/platform_device.h
• linux/pm.h
• linux/slab.h
• linux/virtio.h
• linux/virtio_config.h
• uapi/linux/virtio_mmio.h
• linux/virtio_ring.h

Detected Declarations

• struct virtio_mmio_device
• function device
• function vm_get_features
• function vm_finalize_features
• function vm_get
• function vm_set
• function vm_generation
• function vm_get_status
• function vm_set_status
• function vm_reset
• function vm_notify
• function vm_notify_with_data
• function vm_interrupt
• function vm_del_vq
• function vm_del_vqs
• function vm_synchronize_cbs
• function void
• function vm_find_vqs
• function vm_get_shm_region
• function virtio_mmio_freeze
• function virtio_mmio_restore
• function virtio_mmio_release_dev
• function virtio_mmio_probe
• function virtio_mmio_remove
• function vm_cmdline_set
• function vm_cmdline_get_device
• function vm_cmdline_get
• function vm_unregister_cmdline_device
• function vm_unregister_cmdline_devices
• function vm_unregister_cmdline_devices
• function virtio_mmio_init
• function virtio_mmio_exit
• module init virtio_mmio_init

Annotated Snippet

module_init(virtio_mmio_init);
module_exit(virtio_mmio_exit);

MODULE_AUTHOR("Pawel Moll <pawel.moll@arm.com>");
MODULE_DESCRIPTION("Platform bus driver for memory mapped virtio devices");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/acpi.h`, `linux/dma-mapping.h`, `linux/highmem.h`, `linux/interrupt.h`, `linux/io.h`, `linux/list.h`, `linux/module.h`, `linux/of.h`.
• Detected declarations: `struct virtio_mmio_device`, `function device`, `function vm_get_features`, `function vm_finalize_features`, `function vm_get`, `function vm_set`, `function vm_generation`, `function vm_get_status`, `function vm_set_status`, `function vm_reset`.
• Atlas domain: Driver Families / drivers/virtio.
• Implementation status: integration implementation candidate.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.