arch/um/include/asm/pci.h

File Facts

System

Linux kernel

Corpus path

arch/um/include/asm/pci.h

Extension

.h

Size

469 bytes

Lines

20

Domain

Architecture Layer

Bucket

arch/um

Inferred role

Architecture Layer: implementation source

Status

source implementation candidate

Why This File Exists

CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.

• CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
• 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

• linux/types.h
• asm/io.h
• asm-generic/pci.h

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

#ifndef __ASM_UM_PCI_H
#define __ASM_UM_PCI_H
#include <linux/types.h>
#include <asm/io.h>

/* Generic PCI */
#include <asm-generic/pci.h>

#ifdef CONFIG_PCI_MSI
/*
 * This is a bit of an annoying hack, and it assumes we only have
 * the virt-pci (if anything). Which is true, but still.
 */
void *pci_root_bus_fwnode(struct pci_bus *bus);
#define pci_root_bus_fwnode	pci_root_bus_fwnode
#endif

#endif  /* __ASM_UM_PCI_H */

Annotation

• Immediate include surface: `linux/types.h`, `asm/io.h`, `asm-generic/pci.h`.
• Atlas domain: Architecture Layer / arch/um.
• 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.