arch/arm/include/asm/smp_plat.h

File Facts

System

Linux kernel

Corpus path

arch/arm/include/asm/smp_plat.h

Extension

.h

Size

2535 bytes

Lines

121

Domain

Architecture Layer

Bucket

arch/arm

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/cpumask.h
• linux/err.h
• asm/cpu.h
• asm/cputype.h

Detected Declarations

• struct mpidr_hash
• function is_smp
• function smp_cpuid_part
• function tlb_ops_need_broadcast
• function cache_ops_need_broadcast
• function get_logical_index
• function mpidr_hash_size
• function platform_can_hotplug_cpu

Annotated Snippet

struct mpidr_hash {
	u32	mask; /* used by sleep.S */
	u32	shift_aff[3]; /* used by sleep.S */
	u32	bits;
};

extern struct mpidr_hash mpidr_hash;

static inline u32 mpidr_hash_size(void)
{
	return 1 << mpidr_hash.bits;
}

extern int platform_can_secondary_boot(void);
extern int platform_can_cpu_hotplug(void);

#ifdef CONFIG_HOTPLUG_CPU
extern int platform_can_hotplug_cpu(unsigned int cpu);
#else
static inline int platform_can_hotplug_cpu(unsigned int cpu)
{
	return 0;
}
#endif

#endif

Annotation

• Immediate include surface: `linux/cpumask.h`, `linux/err.h`, `asm/cpu.h`, `asm/cputype.h`.
• Detected declarations: `struct mpidr_hash`, `function is_smp`, `function smp_cpuid_part`, `function tlb_ops_need_broadcast`, `function cache_ops_need_broadcast`, `function get_logical_index`, `function mpidr_hash_size`, `function platform_can_hotplug_cpu`.
• Atlas domain: Architecture Layer / arch/arm.
• Implementation status: source 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.