drivers/misc/vmw_vmci/vmci_guest.c

File Facts

System

Linux kernel

Corpus path

drivers/misc/vmw_vmci/vmci_guest.c

Extension

.c

Size

27415 bytes

Lines

984

Domain

Driver Families

Bucket

drivers/misc

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/vmw_vmci_defs.h
• linux/vmw_vmci_api.h
• linux/moduleparam.h
• linux/interrupt.h
• linux/highmem.h
• linux/kernel.h
• linux/mm.h
• linux/module.h
• linux/processor.h
• linux/sched.h
• linux/slab.h
• linux/init.h
• linux/pci.h
• linux/smp.h
• linux/io.h
• linux/vmalloc.h
• vmci_datagram.h
• vmci_doorbell.h
• vmci_context.h
• vmci_driver.h
• vmci_event.h

Detected Declarations

• struct vmci_guest_device
• function vmci_use_ppn64
• function vmci_guest_code_active
• function vmci_get_vm_context_id
• function vmci_read_reg
• function vmci_write_reg
• function vmci_read_data
• function vmci_write_data
• function vmci_send_datagram
• function vmci_guest_cid_update
• function hypercalls
• function register
• function vmci_process_bitmap
• function interrupt
• function vmci_dispatch_dgs
• function vmci_interrupt_bm
• function vmci_interrupt_dma_datagram
• function vmci_free_dg_buffers
• function vmci_guest_probe_device
• function vmci_guest_remove_device
• function vmci_guest_init
• function vmci_guest_exit
• export vmci_send_datagram

Annotated Snippet

static struct pci_driver vmci_guest_driver = {
	.name		= KBUILD_MODNAME,
	.id_table	= vmci_ids,
	.probe		= vmci_guest_probe_device,
	.remove		= vmci_guest_remove_device,
};

int __init vmci_guest_init(void)
{
	return pci_register_driver(&vmci_guest_driver);
}

void __exit vmci_guest_exit(void)
{
	pci_unregister_driver(&vmci_guest_driver);
}

Annotation

• Immediate include surface: `linux/vmw_vmci_defs.h`, `linux/vmw_vmci_api.h`, `linux/moduleparam.h`, `linux/interrupt.h`, `linux/highmem.h`, `linux/kernel.h`, `linux/mm.h`, `linux/module.h`.
• Detected declarations: `struct vmci_guest_device`, `function vmci_use_ppn64`, `function vmci_guest_code_active`, `function vmci_get_vm_context_id`, `function vmci_read_reg`, `function vmci_write_reg`, `function vmci_read_data`, `function vmci_write_data`, `function vmci_send_datagram`, `function vmci_guest_cid_update`.
• Atlas domain: Driver Families / drivers/misc.
• 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.