arch/sh/kernel/cpu/fpu.c
Source file repositories/reference/linux-study-clean/arch/sh/kernel/cpu/fpu.c
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/kernel/cpu/fpu.c- Extension
.c- Size
- 1821 bytes
- Lines
- 93
- 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/sched/signal.hlinux/sched/task.hlinux/sched/task_stack.hlinux/slab.hasm/processor.hasm/fpu.hasm/traps.hasm/ptrace.h
Detected Declarations
function init_fpufunction __fpu_state_restorefunction fpu_state_restore
Annotated Snippet
if (ret) {
/*
* ran out of memory!
*/
force_sig(SIGKILL);
return;
}
}
grab_fpu(regs);
__fpu_state_restore();
}
BUILD_TRAP_HANDLER(fpu_state_restore)
{
TRAP_HANDLER_DECL;
fpu_state_restore(regs);
}
#endif /* CONFIG_SH_FPU */
Annotation
- Immediate include surface: `linux/sched/signal.h`, `linux/sched/task.h`, `linux/sched/task_stack.h`, `linux/slab.h`, `asm/processor.h`, `asm/fpu.h`, `asm/traps.h`, `asm/ptrace.h`.
- Detected declarations: `function init_fpu`, `function __fpu_state_restore`, `function fpu_state_restore`.
- 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.