arch/mips/kernel/fpu-probe.h
Source file repositories/reference/linux-study-clean/arch/mips/kernel/fpu-probe.h
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/kernel/fpu-probe.h- Extension
.h- Size
- 699 bytes
- Lines
- 41
- Domain
- Architecture Layer
- Bucket
- arch/mips
- 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/kernel.hasm/cpu.hasm/cpu-info.h
Detected Declarations
function cpu_get_fpu_idfunction __cpu_has_fpufunction cpu_set_fpu_opts
Annotated Snippet
#include <linux/kernel.h>
#include <asm/cpu.h>
#include <asm/cpu-info.h>
#ifdef CONFIG_MIPS_FP_SUPPORT
extern int mips_fpu_disabled;
int __cpu_has_fpu(void);
void cpu_set_fpu_opts(struct cpuinfo_mips *c);
void cpu_set_nofpu_opts(struct cpuinfo_mips *c);
#else /* !CONFIG_MIPS_FP_SUPPORT */
#define mips_fpu_disabled 1
static inline unsigned long cpu_get_fpu_id(void)
{
return FPIR_IMP_NONE;
}
static inline int __cpu_has_fpu(void)
{
return 0;
}
static inline void cpu_set_fpu_opts(struct cpuinfo_mips *c)
{
/* no-op */
}
static inline void cpu_set_nofpu_opts(struct cpuinfo_mips *c)
{
/* no-op */
}
#endif /* CONFIG_MIPS_FP_SUPPORT */
Annotation
- Immediate include surface: `linux/kernel.h`, `asm/cpu.h`, `asm/cpu-info.h`.
- Detected declarations: `function cpu_get_fpu_id`, `function __cpu_has_fpu`, `function cpu_set_fpu_opts`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.