arch/arm/kernel/smp.c
Source file repositories/reference/linux-study-clean/arch/arm/kernel/smp.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/kernel/smp.c- Extension
.c- Size
- 19287 bytes
- Lines
- 853
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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/module.hlinux/delay.hlinux/init.hlinux/spinlock.hlinux/sched/mm.hlinux/sched/hotplug.hlinux/sched/task_stack.hlinux/interrupt.hlinux/cache.hlinux/profile.hlinux/errno.hlinux/mm.hlinux/err.hlinux/cpu.hlinux/seq_file.hlinux/irq.hlinux/nmi.hlinux/percpu.hlinux/clockchips.hlinux/completion.hlinux/cpufreq.hlinux/irq_work.hlinux/kernel_stat.hlinux/atomic.hasm/bugs.hasm/smp.hasm/cacheflush.hasm/cpu.hasm/cputype.hasm/exception.hasm/idmap.hasm/topology.h
Detected Declarations
enum ipi_msg_typefunction smp_set_opsfunction get_arch_pgdfunction secondary_biglittle_preparefunction secondary_biglittle_initfunction secondary_biglittle_preparefunction secondary_biglittle_initfunction smp_init_cpusfunction platform_can_secondary_bootfunction platform_can_cpu_hotplugfunction platform_cpu_killfunction platform_cpu_disablefunction platform_can_hotplug_cpufunction ipi_teardownfunction __cpu_disablefunction arch_cpuhp_cleanup_dead_cpufunction arch_cpu_idle_deadfunction smp_store_cpu_infofunction set_currentfunction secondary_start_kernelfunction smp_cpus_donefunction smp_prepare_boot_cpufunction smp_prepare_cpusfunction show_ipi_listfunction arch_send_call_function_ipi_maskfunction arch_send_wakeup_ipi_maskfunction arch_send_call_function_single_ipifunction arch_irq_work_raisefunction tick_broadcastfunction ipi_cpu_stopfunction register_ipi_completionfunction ipi_completefunction do_handle_IPIfunction handle_IPIfunction ipi_handlerfunction smp_cross_callfunction ipi_setupfunction set_smp_ipi_rangefunction arch_smp_send_reschedulefunction smp_send_stopfunction panic_smp_self_stopfunction cpufreq_callbackfunction register_cpufreq_notifierfunction raise_nmifunction arch_trigger_cpumask_backtracemodule init register_cpufreq_notifier
Annotated Snippet
core_initcall(register_cpufreq_notifier);
#endif
static void raise_nmi(cpumask_t *mask)
{
__ipi_send_mask(ipi_desc[IPI_CPU_BACKTRACE], mask);
}
void arch_trigger_cpumask_backtrace(const cpumask_t *mask, int exclude_cpu)
{
nmi_trigger_cpumask_backtrace(mask, exclude_cpu, raise_nmi);
}
Annotation
- Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/init.h`, `linux/spinlock.h`, `linux/sched/mm.h`, `linux/sched/hotplug.h`, `linux/sched/task_stack.h`, `linux/interrupt.h`.
- Detected declarations: `enum ipi_msg_type`, `function smp_set_ops`, `function get_arch_pgd`, `function secondary_biglittle_prepare`, `function secondary_biglittle_init`, `function secondary_biglittle_prepare`, `function secondary_biglittle_init`, `function smp_init_cpus`, `function platform_can_secondary_boot`, `function platform_can_cpu_hotplug`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.