arch/powerpc/kernel/pci-common.c
Source file repositories/reference/linux-study-clean/arch/powerpc/kernel/pci-common.c
File Facts
- System
- Linux kernel
- Corpus path
arch/powerpc/kernel/pci-common.c- Extension
.c- Size
- 47546 bytes
- Lines
- 1740
- Domain
- Architecture Layer
- Bucket
- arch/powerpc
- Inferred role
- Architecture Layer: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/kernel.hlinux/pci.hlinux/string.hlinux/init.hlinux/delay.hlinux/export.hlinux/of_address.hlinux/of_pci.hlinux/mm.hlinux/shmem_fs.hlinux/list.hlinux/syscalls.hlinux/irq.hlinux/vmalloc.hlinux/slab.hlinux/vgaarb.hlinux/numa.hlinux/msi.hlinux/irqdomain.hasm/processor.hasm/io.hasm/pci-bridge.hasm/byteorder.hasm/machdep.hasm/ppc-pci.hasm/eeh.hasm/setup.h../../../drivers/pci/pci.h
Detected Declarations
struct pci_intx_virqfunction set_pci_dma_opsfunction get_phb_numberfunction pcibios_free_controllerfunction pci_create_root_busfunction pcibios_window_alignmentfunction pcibios_setup_bridgefunction pcibios_reset_secondary_busfunction pcibios_default_alignmentfunction pcibios_iov_resource_alignmentfunction pcibios_sriov_enablefunction pcibios_sriov_disablefunction pcibios_io_sizefunction pcibios_vaddr_is_ioportfunction pci_address_to_piofunction pci_domain_nrfunction pci_find_hose_for_OF_devicefunction ppc_pci_intx_releasefunction ppc_pci_unmap_irq_linefunction list_for_each_entryfunction ppc_pci_register_irq_notifierfunction pci_read_irq_linefunction pci_iobar_pfnfunction pci_phys_mem_access_protfunction pci_legacy_readfunction pci_legacy_writefunction pci_mmap_legacy_page_rangefunction pci_resource_to_userfunction pci_process_bridge_OF_rangesfunction pci_proc_domainfunction pcibios_root_bridge_preparefunction pcibios_fixup_resourcesfunction pci_dev_for_each_resourcefunction pcibios_uninitialized_bridge_resourcefunction pcibios_fixup_bridgefunction pci_bus_for_each_resourcefunction pcibios_setup_bus_selffunction pcibios_bus_add_devicefunction pcibios_device_addfunction pcibios_set_masterfunction skip_isa_ioresource_alignfunction pcibios_align_resourcefunction reparent_resourcesfunction pcibios_allocate_bus_resourcesfunction pci_bus_for_each_resourcefunction alloc_resourcefunction request_resourcefunction pcibios_allocate_resources
Annotated Snippet
core_initcall(discover_phbs);
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/pci.h`, `linux/string.h`, `linux/init.h`, `linux/delay.h`, `linux/export.h`, `linux/of_address.h`, `linux/of_pci.h`.
- Detected declarations: `struct pci_intx_virq`, `function set_pci_dma_ops`, `function get_phb_number`, `function pcibios_free_controller`, `function pci_create_root_bus`, `function pcibios_window_alignment`, `function pcibios_setup_bridge`, `function pcibios_reset_secondary_bus`, `function pcibios_default_alignment`, `function pcibios_iov_resource_alignment`.
- Atlas domain: Architecture Layer / arch/powerpc.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
- 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.