arch/arm64/include/asm/setup.h
Source file repositories/reference/linux-study-clean/arch/arm64/include/asm/setup.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/include/asm/setup.h- Extension
.h- Size
- 792 bytes
- Lines
- 45
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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.
Dependency Surface
linux/string.huapi/asm/setup.h
Detected Declarations
function arch_parse_debug_rodata
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#ifndef __ARM64_ASM_SETUP_H
#define __ARM64_ASM_SETUP_H
#include <linux/string.h>
#include <uapi/asm/setup.h>
/*
* These two variables are used in the head.S file.
*/
extern phys_addr_t __fdt_pointer __initdata;
extern u64 __cacheline_aligned boot_args[4];
static inline bool arch_parse_debug_rodata(char *arg)
{
extern bool rodata_enabled;
extern bool rodata_full;
if (!arg)
return false;
if (!strcmp(arg, "on")) {
rodata_enabled = rodata_full = true;
return true;
}
if (!strcmp(arg, "off")) {
rodata_enabled = rodata_full = false;
return true;
}
if (!strcmp(arg, "noalias")) {
rodata_enabled = true;
rodata_full = false;
return true;
}
return false;
}
#define arch_parse_debug_rodata arch_parse_debug_rodata
#endif
Annotation
- Immediate include surface: `linux/string.h`, `uapi/asm/setup.h`.
- Detected declarations: `function arch_parse_debug_rodata`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.