arch/riscv/kernel/kernel_mode_fpu.c
Source file repositories/reference/linux-study-clean/arch/riscv/kernel/kernel_mode_fpu.c
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/kernel/kernel_mode_fpu.c- Extension
.c- Size
- 560 bytes
- Lines
- 29
- Domain
- Architecture Layer
- Bucket
- arch/riscv
- 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.
Dependency Surface
linux/export.hlinux/preempt.hasm/csr.hasm/fpu.hasm/processor.hasm/switch_to.h
Detected Declarations
function Copyrightfunction kernel_fpu_endexport kernel_fpu_beginexport kernel_fpu_end
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/*
* Copyright (C) 2023 SiFive
*/
#include <linux/export.h>
#include <linux/preempt.h>
#include <asm/csr.h>
#include <asm/fpu.h>
#include <asm/processor.h>
#include <asm/switch_to.h>
void kernel_fpu_begin(void)
{
preempt_disable();
fstate_save(current, task_pt_regs(current));
csr_set(CSR_SSTATUS, SR_FS);
}
EXPORT_SYMBOL_GPL(kernel_fpu_begin);
void kernel_fpu_end(void)
{
csr_clear(CSR_SSTATUS, SR_FS);
fstate_restore(current, task_pt_regs(current));
preempt_enable();
}
EXPORT_SYMBOL_GPL(kernel_fpu_end);
Annotation
- Immediate include surface: `linux/export.h`, `linux/preempt.h`, `asm/csr.h`, `asm/fpu.h`, `asm/processor.h`, `asm/switch_to.h`.
- Detected declarations: `function Copyright`, `function kernel_fpu_end`, `export kernel_fpu_begin`, `export kernel_fpu_end`.
- Atlas domain: Architecture Layer / arch/riscv.
- Implementation status: integration 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.