drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c

File Facts

System

Linux kernel

Corpus path

drivers/infiniband/hw/vmw_pvrdma/pvrdma_main.c

Extension

.c

Size

31199 bytes

Lines

1157

Domain

Driver Families

Bucket

drivers/infiniband

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/errno.h
• linux/inetdevice.h
• linux/init.h
• linux/module.h
• linux/slab.h
• rdma/ib_addr.h
• rdma/ib_smi.h
• rdma/ib_user_verbs.h
• net/addrconf.h
• pvrdma.h

Detected Declarations

• function hca_type_show
• function hw_rev_show
• function board_id_show
• function pvrdma_get_fw_ver_str
• function pvrdma_init_device
• function pvrdma_port_immutable
• function pvrdma_dispatch_event
• function pvrdma_report_event_handle
• function pvrdma_register_device
• function pvrdma_intr0_handler
• function pvrdma_qp_event
• function pvrdma_cq_event
• function pvrdma_srq_event
• function pvrdma_dev_event
• function pvrdma_intr1_handler
• function pvrdma_intrx_handler
• function pvrdma_free_irq
• function pvrdma_enable_intrs
• function pvrdma_disable_intrs
• function pvrdma_alloc_intrs
• function pvrdma_free_slots
• function pvrdma_add_gid_at_index
• function pvrdma_add_gid
• function pvrdma_del_gid_at_index
• function pvrdma_del_gid
• function pvrdma_netdevice_event_handle
• function pvrdma_netdevice_event_work
• function pvrdma_netdevice_event
• function pvrdma_pci_probe
• function pvrdma_pci_remove
• function pvrdma_init
• function pvrdma_cleanup
• module init pvrdma_init

Annotated Snippet

static struct pci_driver pvrdma_driver = {
	.name		= DRV_NAME,
	.id_table	= pvrdma_pci_table,
	.probe		= pvrdma_pci_probe,
	.remove		= pvrdma_pci_remove,
};

static int __init pvrdma_init(void)
{
	int err;

	event_wq = alloc_ordered_workqueue("pvrdma_event_wq", WQ_MEM_RECLAIM);
	if (!event_wq)
		return -ENOMEM;

	err = pci_register_driver(&pvrdma_driver);
	if (err)
		destroy_workqueue(event_wq);

	return err;
}

static void __exit pvrdma_cleanup(void)
{
	pci_unregister_driver(&pvrdma_driver);

	destroy_workqueue(event_wq);
}

module_init(pvrdma_init);
module_exit(pvrdma_cleanup);

MODULE_AUTHOR("VMware, Inc");
MODULE_DESCRIPTION("VMware Paravirtual RDMA driver");
MODULE_LICENSE("Dual BSD/GPL");

Annotation

• Immediate include surface: `linux/errno.h`, `linux/inetdevice.h`, `linux/init.h`, `linux/module.h`, `linux/slab.h`, `rdma/ib_addr.h`, `rdma/ib_smi.h`, `rdma/ib_user_verbs.h`.
• Detected declarations: `function hca_type_show`, `function hw_rev_show`, `function board_id_show`, `function pvrdma_get_fw_ver_str`, `function pvrdma_init_device`, `function pvrdma_port_immutable`, `function pvrdma_dispatch_event`, `function pvrdma_report_event_handle`, `function pvrdma_register_device`, `function pvrdma_intr0_handler`.
• Atlas domain: Driver Families / drivers/infiniband.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.