arch/x86/pci/mmconfig_64.c
Source file repositories/reference/linux-study-clean/arch/x86/pci/mmconfig_64.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/pci/mmconfig_64.c- Extension
.c- Size
- 3257 bytes
- Lines
- 155
- Domain
- Architecture Layer
- Bucket
- arch/x86
- 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.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/pci.hlinux/init.hlinux/acpi.hlinux/bitmap.hlinux/rcupdate.hasm/e820/api.hasm/pci_x86.h
Detected Declarations
function pci_mmcfg_readfunction pci_mmcfg_writefunction pci_mmcfg_arch_mapfunction pci_mmcfg_arch_unmapfunction pci_mmcfg_arch_initfunction list_for_each_entryfunction pci_mmcfg_arch_free
Annotated Snippet
if (pci_mmcfg_arch_map(cfg)) {
pci_mmcfg_arch_free();
return 0;
}
raw_pci_ext_ops = &pci_mmcfg;
return 1;
}
void __init pci_mmcfg_arch_free(void)
{
struct pci_mmcfg_region *cfg;
list_for_each_entry(cfg, &pci_mmcfg_list, list)
pci_mmcfg_arch_unmap(cfg);
}
Annotation
- Immediate include surface: `linux/pci.h`, `linux/init.h`, `linux/acpi.h`, `linux/bitmap.h`, `linux/rcupdate.h`, `asm/e820/api.h`, `asm/pci_x86.h`.
- Detected declarations: `function pci_mmcfg_read`, `function pci_mmcfg_write`, `function pci_mmcfg_arch_map`, `function pci_mmcfg_arch_unmap`, `function pci_mmcfg_arch_init`, `function list_for_each_entry`, `function pci_mmcfg_arch_free`.
- Atlas domain: Architecture Layer / arch/x86.
- Implementation status: source implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.