arch/x86/kernel/apic/probe_32.c
Source file repositories/reference/linux-study-clean/arch/x86/kernel/apic/probe_32.c
File Facts
- System
- Linux kernel
- Corpus path
arch/x86/kernel/apic/probe_32.c- Extension
.c- Size
- 2474 bytes
- Lines
- 112
- Domain
- Architecture Layer
- Bucket
- arch/x86
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/export.hlinux/errno.hlinux/smp.hxen/xen.hasm/io_apic.hasm/apic.hasm/acpi.hlocal.h
Detected Declarations
function default_get_apic_idfunction probe_defaultfunction parse_apicfunction x86_32_probe_apicexport apic
Annotated Snippet
if (!strcmp((*drv)->name, arg)) {
apic_install_driver(*drv);
cmdline_apic = 1;
return 0;
}
}
/* Parsed again by __setup for debug/verbose */
return 0;
}
early_param("apic", parse_apic);
void __init x86_32_probe_apic(void)
{
if (!cmdline_apic) {
struct apic **drv;
for (drv = __apicdrivers; drv < __apicdrivers_end; drv++) {
if ((*drv)->probe()) {
apic_install_driver(*drv);
break;
}
}
/* Not visible without early console */
if (drv == __apicdrivers_end)
panic("Didn't find an APIC driver");
}
}
Annotation
- Immediate include surface: `linux/export.h`, `linux/errno.h`, `linux/smp.h`, `xen/xen.h`, `asm/io_apic.h`, `asm/apic.h`, `asm/acpi.h`, `local.h`.
- Detected declarations: `function default_get_apic_id`, `function probe_default`, `function parse_apic`, `function x86_32_probe_apic`, `export apic`.
- Atlas domain: Architecture Layer / arch/x86.
- Implementation status: integration 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.