arch/sparc/include/asm/adi_64.h
Source file repositories/reference/linux-study-clean/arch/sparc/include/asm/adi_64.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sparc/include/asm/adi_64.h- Extension
.h- Size
- 814 bytes
- Lines
- 47
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.h
Detected Declarations
struct adi_capsstruct adi_configfunction adi_capablefunction adi_blksizefunction adi_nbits
Annotated Snippet
struct adi_caps {
__u64 blksz;
__u64 nbits;
__u64 ue_on_adi;
};
struct adi_config {
bool enabled;
struct adi_caps caps;
};
extern struct adi_config adi_state;
extern void mdesc_adi_init(void);
static inline bool adi_capable(void)
{
return adi_state.enabled;
}
static inline unsigned long adi_blksize(void)
{
return adi_state.caps.blksz;
}
static inline unsigned long adi_nbits(void)
{
return adi_state.caps.nbits;
}
#endif /* __ASSEMBLER__ */
#endif /* !(__ASM_SPARC64_ADI_H) */
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct adi_caps`, `struct adi_config`, `function adi_capable`, `function adi_blksize`, `function adi_nbits`.
- 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.