drivers/vdpa/ifcvf/ifcvf_main.c

File Facts

System

Linux kernel

Corpus path

drivers/vdpa/ifcvf/ifcvf_main.c

Extension

.c

Size

21735 bytes

Lines

907

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/sysfs.h
• ifcvf_base.h

Detected Declarations

• function Copyright
• function ifcvf_vq_intr_handler
• function ifcvf_vqs_reused_intr_handler
• function ifcvf_dev_intr_handler
• function ifcvf_free_irq_vectors
• function ifcvf_free_per_vq_irq
• function ifcvf_free_vqs_reused_irq
• function ifcvf_free_vq_irq
• function ifcvf_free_config_irq
• function ifcvf_free_irq
• function ifcvf_alloc_vectors
• function ifcvf_request_per_vq_irq
• function ifcvf_request_vqs_reused_irq
• function ifcvf_request_dev_irq
• function ifcvf_request_vq_irq
• function ifcvf_request_config_irq
• function ifcvf_request_irq
• function ifcvf_vdpa_get_device_features
• function ifcvf_vdpa_set_driver_features
• function ifcvf_vdpa_get_driver_features
• function ifcvf_vdpa_get_status
• function ifcvf_vdpa_set_status
• function ifcvf_vdpa_reset
• function ifcvf_vdpa_get_vq_num_max
• function ifcvf_vdpa_get_vq_num_min
• function ifcvf_vdpa_get_vq_state
• function ifcvf_vdpa_set_vq_state
• function ifcvf_vdpa_set_vq_cb
• function ifcvf_vdpa_set_vq_ready
• function ifcvf_vdpa_get_vq_ready
• function ifcvf_vdpa_set_vq_num
• function ifcvf_vdpa_set_vq_address
• function ifcvf_vdpa_kick_vq
• function ifcvf_vdpa_get_generation
• function ifcvf_vdpa_get_device_id
• function ifcvf_vdpa_get_vendor_id
• function ifcvf_vdpa_get_vq_align
• function ifcvf_vdpa_get_config_size
• function ifcvf_vdpa_get_vq_group
• function ifcvf_vdpa_get_config
• function ifcvf_vdpa_set_config
• function ifcvf_vdpa_set_config_cb
• function ifcvf_vdpa_get_vq_irq
• function ifcvf_vdpa_get_vq_size
• function ifcvf_get_vq_notification
• function get_dev_type
• function ifcvf_vdpa_dev_add
• function ifcvf_vdpa_dev_del

Annotated Snippet

static struct pci_driver ifcvf_driver = {
	.name     = IFCVF_DRIVER_NAME,
	.id_table = ifcvf_pci_ids,
	.probe    = ifcvf_probe,
	.remove   = ifcvf_remove,
};

module_pci_driver(ifcvf_driver);

MODULE_DESCRIPTION("Intel IFC VF NIC driver for virtio dataplane offloading");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/interrupt.h`, `linux/module.h`, `linux/pci.h`, `linux/sysfs.h`, `ifcvf_base.h`.
• Detected declarations: `function Copyright`, `function ifcvf_vq_intr_handler`, `function ifcvf_vqs_reused_intr_handler`, `function ifcvf_dev_intr_handler`, `function ifcvf_free_irq_vectors`, `function ifcvf_free_per_vq_irq`, `function ifcvf_free_vqs_reused_irq`, `function ifcvf_free_vq_irq`, `function ifcvf_free_config_irq`, `function ifcvf_free_irq`.
• 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.