arch/sparc/kernel/setup.c
Source file repositories/reference/linux-study-clean/arch/sparc/kernel/setup.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sparc/kernel/setup.c- Extension
.c- Size
- 869 bytes
- Lines
- 47
- Domain
- Architecture Layer
- Bucket
- arch/sparc
- 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
asm/setup.hlinux/sysctl.h
Detected Declarations
function init_sparc_sysctls
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include <asm/setup.h>
#include <linux/sysctl.h>
static const struct ctl_table sparc_sysctl_table[] = {
{
.procname = "reboot-cmd",
.data = reboot_command,
.maxlen = 256,
.mode = 0644,
.proc_handler = proc_dostring,
},
{
.procname = "stop-a",
.data = &stop_a_enabled,
.maxlen = sizeof(int),
.mode = 0644,
.proc_handler = proc_dointvec,
},
{
.procname = "scons-poweroff",
.data = &scons_pwroff,
.maxlen = sizeof(int),
.mode = 0644,
.proc_handler = proc_dointvec,
},
#ifdef CONFIG_SPARC64
{
.procname = "tsb-ratio",
.data = &sysctl_tsb_ratio,
.maxlen = sizeof(int),
.mode = 0644,
.proc_handler = proc_dointvec,
},
#endif
};
static int __init init_sparc_sysctls(void)
{
register_sysctl_init("kernel", sparc_sysctl_table);
return 0;
}
arch_initcall(init_sparc_sysctls);
Annotation
- Immediate include surface: `asm/setup.h`, `linux/sysctl.h`.
- Detected declarations: `function init_sparc_sysctls`.
- Atlas domain: Architecture Layer / arch/sparc.
- 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.