drivers/misc/vmw_vmci/vmci_doorbell.h

File Facts

System

Linux kernel

Corpus path

drivers/misc/vmw_vmci/vmci_doorbell.h

Extension

.h

Size

1062 bytes

Lines

44

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/vmw_vmci_defs.h
• linux/types.h
• vmci_driver.h

Detected Declarations

• struct vmci_dbell_notify_resource_info
• struct dbell_cpt_state

Annotated Snippet

struct vmci_dbell_notify_resource_info {
	struct vmci_handle handle;
	u16 resource;
	u16 action;
	s32 result;
};

/*
 * Structure used for checkpointing the doorbell mappings. It is
 * written to the checkpoint as is, so changing this structure will
 * break checkpoint compatibility.
 */
struct dbell_cpt_state {
	struct vmci_handle handle;
	u64 bitmap_idx;
};

int vmci_dbell_host_context_notify(u32 src_cid, struct vmci_handle handle);
int vmci_dbell_get_priv_flags(struct vmci_handle handle, u32 *priv_flags);

bool vmci_dbell_register_notification_bitmap(u64 bitmap_ppn);
void vmci_dbell_scan_notification_entries(u8 *bitmap);

#endif /* VMCI_DOORBELL_H */

Annotation

• Immediate include surface: `linux/vmw_vmci_defs.h`, `linux/types.h`, `vmci_driver.h`.
• Detected declarations: `struct vmci_dbell_notify_resource_info`, `struct dbell_cpt_state`.
• 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.