arch/sparc/kernel/sstate.c

File Facts

System

Linux kernel

Corpus path

arch/sparc/kernel/sstate.c

Extension

.c

Size

2715 bytes

Lines

125

Domain

Architecture Layer

Bucket

arch/sparc

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

Dependency Surface

• linux/kernel.h
• linux/notifier.h
• linux/panic_notifier.h
• linux/reboot.h
• linux/init.h
• asm/hypervisor.h
• asm/spitfire.h
• asm/oplib.h
• asm/head.h
• asm/io.h
• kernel.h

Detected Declarations

• function do_set_sstate
• function sstate_reboot_call
• function sstate_panic_event
• function sstate_init
• function sstate_running
• module init sstate_init

Annotated Snippet

core_initcall(sstate_init);

static int __init sstate_running(void)
{
	do_set_sstate(HV_SOFT_STATE_NORMAL, running_msg);
	return 0;
}

late_initcall(sstate_running);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/notifier.h`, `linux/panic_notifier.h`, `linux/reboot.h`, `linux/init.h`, `asm/hypervisor.h`, `asm/spitfire.h`, `asm/oplib.h`.
• Detected declarations: `function do_set_sstate`, `function sstate_reboot_call`, `function sstate_panic_event`, `function sstate_init`, `function sstate_running`, `module init sstate_init`.
• Atlas domain: Architecture Layer / arch/sparc.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.