arch/sparc/include/asm/asm-prototypes.h
Source file repositories/reference/linux-study-clean/arch/sparc/include/asm/asm-prototypes.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sparc/include/asm/asm-prototypes.h- Extension
.h- Size
- 833 bytes
- Lines
- 32
- Domain
- Architecture Layer
- Bucket
- arch/sparc
- 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.
Dependency Surface
linux/atomic.hlinux/uaccess.hasm/atomic.hasm/cacheflush.hasm/checksum.hasm/delay.hasm/ftrace.hasm/oplib.hasm/pgtable.hasm/trap_block.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#include <linux/atomic.h>
#include <linux/uaccess.h>
#include <asm/atomic.h>
#include <asm/cacheflush.h>
#include <asm/checksum.h>
#include <asm/delay.h>
#include <asm/ftrace.h>
#include <asm/oplib.h>
#include <asm/pgtable.h>
#include <asm/trap_block.h>
void *__memscan_zero(void *, size_t);
void *__memscan_generic(void *, int, size_t);
void *__bzero(void *, size_t);
void VISenter(void); /* Dummy prototype to supress warning */
#undef memcpy
#undef memset
void *memcpy(void *dest, const void *src, size_t n);
void *memset(void *s, int c, size_t n);
typedef int TItype __attribute__((mode(TI)));
TItype __multi3(TItype a, TItype b);
s64 __ashldi3(s64, int);
s64 __lshrdi3(s64, int);
s64 __ashrdi3(s64, int);
Annotation
- Immediate include surface: `linux/atomic.h`, `linux/uaccess.h`, `asm/atomic.h`, `asm/cacheflush.h`, `asm/checksum.h`, `asm/delay.h`, `asm/ftrace.h`, `asm/oplib.h`.
- Atlas domain: Architecture Layer / arch/sparc.
- 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.