drivers/misc/vmw_vmci/vmci_driver.c

File Facts

System

Linux kernel

Corpus path

drivers/misc/vmw_vmci/vmci_driver.c

Extension

.c

Size

4148 bytes

Lines

177

Domain

Driver Families

Bucket

drivers/misc

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.

Dependency Surface

• linux/vmw_vmci_defs.h
• linux/vmw_vmci_api.h
• linux/atomic.h
• linux/kernel.h
• linux/module.h
• linux/init.h
• vmci_driver.h
• vmci_event.h

Detected Declarations

• function vmci_get_context_id
• function vmci_register_vsock_callback
• function vmci_call_vsock_callback
• function vmci_drv_init
• function vmci_drv_exit
• module init vmci_drv_init
• export vmci_get_context_id
• export vmci_register_vsock_callback

Annotated Snippet

module_init(vmci_drv_init);

static void __exit vmci_drv_exit(void)
{
	if (vmci_guest_personality_initialized)
		vmci_guest_exit();

	if (vmci_host_personality_initialized)
		vmci_host_exit();

	vmci_event_exit();
}
module_exit(vmci_drv_exit);

MODULE_AUTHOR("VMware, Inc.");
MODULE_DESCRIPTION("VMware Virtual Machine Communication Interface.");
MODULE_VERSION("1.1.6.0-k");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/vmw_vmci_defs.h`, `linux/vmw_vmci_api.h`, `linux/atomic.h`, `linux/kernel.h`, `linux/module.h`, `linux/init.h`, `vmci_driver.h`, `vmci_event.h`.
• Detected declarations: `function vmci_get_context_id`, `function vmci_register_vsock_callback`, `function vmci_call_vsock_callback`, `function vmci_drv_init`, `function vmci_drv_exit`, `module init vmci_drv_init`, `export vmci_get_context_id`, `export vmci_register_vsock_callback`.
• Atlas domain: Driver Families / drivers/misc.
• Implementation status: integration implementation candidate.
• 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.