drivers/misc/vmw_vmci/vmci_datagram.h

File Facts

System

Linux kernel

Corpus path

drivers/misc/vmw_vmci/vmci_datagram.h

Extension

.h

Size

1228 bytes

Lines

45

Domain

Driver Families

Bucket

drivers/misc

Inferred role

Driver Families: implementation source

Status

source 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 or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/types.h
• linux/list.h
• vmci_context.h

Detected Declarations

• struct vmci_datagram_queue_entry
• struct vmci_datagram_snd_rcv_info

Annotated Snippet

struct vmci_datagram_queue_entry {
	struct list_head list_item;	/* For queuing. */
	size_t dg_size;		/* Size of datagram. */
	struct vmci_datagram *dg;	/* Pending datagram. */
};

/* VMCIDatagramSendRecvInfo */
struct vmci_datagram_snd_rcv_info {
	u64 addr;
	u32 len;
	s32 result;
};

/* Datagram API for non-public use. */
int vmci_datagram_dispatch(u32 context_id, struct vmci_datagram *dg,
			   bool from_guest);
int vmci_datagram_invoke_guest_handler(struct vmci_datagram *dg);

#endif /* _VMCI_DATAGRAM_H_ */

Annotation

• Immediate include surface: `linux/types.h`, `linux/list.h`, `vmci_context.h`.
• Detected declarations: `struct vmci_datagram_queue_entry`, `struct vmci_datagram_snd_rcv_info`.
• Atlas domain: Driver Families / drivers/misc.
• Implementation status: source implementation candidate.

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.