arch/sh/include/asm/smp.h
Source file repositories/reference/linux-study-clean/arch/sh/include/asm/smp.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/include/asm/smp.h- Extension
.h- Size
- 1847 bytes
- Lines
- 84
- Domain
- Architecture Layer
- Bucket
- arch/sh
- 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/bitops.hlinux/cpumask.hasm/smp-ops.hlinux/atomic.hasm/current.hasm/percpu.h
Detected Declarations
struct of_cpu_methodfunction __cpu_diefunction hard_smp_processor_id
Annotated Snippet
struct of_cpu_method {
const char *method;
struct plat_smp_ops *ops;
};
#define CPU_METHOD_OF_DECLARE(name, _method, _ops) \
static const struct of_cpu_method __cpu_method_of_table_##name \
__used __section("__cpu_method_of_table") \
= { .method = _method, .ops = _ops }
#else
#define hard_smp_processor_id() (0)
#endif /* CONFIG_SMP */
#endif /* __ASM_SH_SMP_H */
Annotation
- Immediate include surface: `linux/bitops.h`, `linux/cpumask.h`, `asm/smp-ops.h`, `linux/atomic.h`, `asm/current.h`, `asm/percpu.h`.
- Detected declarations: `struct of_cpu_method`, `function __cpu_die`, `function hard_smp_processor_id`.
- Atlas domain: Architecture Layer / arch/sh.
- 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.