include/linux/msi_api.h

File Facts

System

Linux kernel

Corpus path

include/linux/msi_api.h

Extension

.h

Size

1981 bytes

Lines

73

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct device
• struct msi_map
• enum msi_domain_ids
• function msi_get_virq

Annotated Snippet

struct msi_map {
	int	index;
	int	virq;
};

/*
 * Constant to be used for dynamic allocations when the allocation is any
 * free MSI index, which is either an entry in a hardware table or a
 * software managed index.
 */
#define MSI_ANY_INDEX		UINT_MAX

unsigned int msi_domain_get_virq(struct device *dev, unsigned int domid, unsigned int index);

/**
 * msi_get_virq - Lookup the Linux interrupt number for a MSI index on the default interrupt domain
 * @dev:	Device for which the lookup happens
 * @index:	The MSI index to lookup
 *
 * Return: The Linux interrupt number on success (> 0), 0 if not found
 */
static inline unsigned int msi_get_virq(struct device *dev, unsigned int index)
{
	return msi_domain_get_virq(dev, MSI_DEFAULT_DOMAIN, index);
}

#endif

Annotation

• Detected declarations: `struct device`, `struct msi_map`, `enum msi_domain_ids`, `function msi_get_virq`.
• Atlas domain: Core OS / Core Kernel Interface.
• Implementation status: source implementation candidate.
• 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.