drivers/vdpa/virtio_pci/vp_vdpa.c

File Facts

System

Linux kernel

Corpus path

drivers/vdpa/virtio_pci/vp_vdpa.c

Extension

.c

Size

17732 bytes

Lines

703

Domain

Driver Families

Bucket

drivers/vdpa

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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/interrupt.h
• linux/module.h
• linux/pci.h
• linux/vdpa.h
• linux/virtio.h
• linux/virtio_config.h
• linux/virtio_ring.h
• linux/virtio_pci.h
• linux/virtio_pci_modern.h
• uapi/linux/vdpa.h

Detected Declarations

• struct vp_vring
• struct vp_vdpa
• struct vp_vdpa_mgmtdev
• function vp_vdpa_get_device_features
• function vp_vdpa_set_driver_features
• function vp_vdpa_get_driver_features
• function vp_vdpa_get_status
• function vp_vdpa_get_vq_irq
• function vp_vdpa_free_irq
• function vp_vdpa_vq_handler
• function vp_vdpa_config_handler
• function vp_vdpa_request_irq
• function vp_vdpa_set_status
• function vp_vdpa_reset
• function vp_vdpa_get_vq_num_max
• function vp_vdpa_get_vq_state
• function vp_vdpa_set_vq_state_split
• function vp_vdpa_set_vq_state_packed
• function vp_vdpa_set_vq_state
• function vp_vdpa_set_vq_cb
• function vp_vdpa_set_vq_ready
• function vp_vdpa_get_vq_ready
• function vp_vdpa_set_vq_num
• function vp_vdpa_get_vq_size
• function vp_vdpa_set_vq_address
• function vp_vdpa_kick_vq
• function vp_vdpa_kick_vq_with_data
• function vp_vdpa_get_generation
• function vp_vdpa_get_device_id
• function vp_vdpa_get_vendor_id
• function vp_vdpa_get_vq_align
• function vp_vdpa_get_config_size
• function vp_vdpa_get_config
• function vp_vdpa_set_config
• function vp_vdpa_set_config_cb
• function vp_vdpa_get_vq_notification
• function vp_vdpa_free_irq_vectors
• function vp_vdpa_dev_add
• function vp_vdpa_dev_del
• function vp_vdpa_probe
• function vp_vdpa_remove

Annotated Snippet

static struct pci_driver vp_vdpa_driver = {
	.name		= "vp-vdpa",
	.id_table	= NULL, /* only dynamic ids */
	.probe		= vp_vdpa_probe,
	.remove		= vp_vdpa_remove,
};

module_pci_driver(vp_vdpa_driver);

MODULE_AUTHOR("Jason Wang <jasowang@redhat.com>");
MODULE_DESCRIPTION("vp-vdpa");
MODULE_LICENSE("GPL");
MODULE_VERSION("1");

Annotation

• Immediate include surface: `linux/interrupt.h`, `linux/module.h`, `linux/pci.h`, `linux/vdpa.h`, `linux/virtio.h`, `linux/virtio_config.h`, `linux/virtio_ring.h`, `linux/virtio_pci.h`.
• Detected declarations: `struct vp_vring`, `struct vp_vdpa`, `struct vp_vdpa_mgmtdev`, `function vp_vdpa_get_device_features`, `function vp_vdpa_set_driver_features`, `function vp_vdpa_get_driver_features`, `function vp_vdpa_get_status`, `function vp_vdpa_get_vq_irq`, `function vp_vdpa_free_irq`, `function vp_vdpa_vq_handler`.
• Atlas domain: Driver Families / drivers/vdpa.
• Implementation status: pattern 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.