arch/arm64/include/asm/simd.h
Source file repositories/reference/linux-study-clean/arch/arm64/include/asm/simd.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/include/asm/simd.h- Extension
.h- Size
- 1484 bytes
- Lines
- 61
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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/cleanup.hlinux/compiler.hlinux/irqflags.hlinux/percpu.hlinux/preempt.hlinux/types.hasm/neon.h
Detected Declarations
function Copyrightfunction may_use_simd
Annotated Snippet
static __must_check inline bool may_use_simd(void) {
return false;
}
#endif /* ! CONFIG_KERNEL_MODE_NEON */
DEFINE_LOCK_GUARD_1(ksimd,
struct user_fpsimd_state,
kernel_neon_begin(_T->lock),
kernel_neon_end(_T->lock))
#define __scoped_ksimd(_label) \
for (struct user_fpsimd_state __uninitialized __st; \
true; ({ goto _label; })) \
if (0) { \
_label: break; \
} else scoped_guard(ksimd, &__st)
#define scoped_ksimd() __scoped_ksimd(__UNIQUE_ID(label))
#endif
Annotation
- Immediate include surface: `linux/cleanup.h`, `linux/compiler.h`, `linux/irqflags.h`, `linux/percpu.h`, `linux/preempt.h`, `linux/types.h`, `asm/neon.h`.
- Detected declarations: `function Copyright`, `function may_use_simd`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.