arch/arm/include/asm/efi.h
Source file repositories/reference/linux-study-clean/arch/arm/include/asm/efi.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/include/asm/efi.h- Extension
.h- Size
- 2678 bytes
- Lines
- 95
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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
asm/cacheflush.hasm/cachetype.hasm/early_ioremap.hasm/fixmap.hasm/highmem.hasm/mach/map.hasm/mmu_context.hasm/ptrace.hasm/uaccess.h
Detected Declarations
struct efi_arm_entry_statefunction efi_set_pgdfunction efi_get_max_initrd_addrfunction efi_capsule_flush_cache_range
Annotated Snippet
struct efi_arm_entry_state {
u32 cpsr_before_ebs;
u32 sctlr_before_ebs;
u32 cpsr_after_ebs;
u32 sctlr_after_ebs;
};
static inline void efi_capsule_flush_cache_range(void *addr, int size)
{
__cpuc_flush_dcache_area(addr, size);
}
#endif /* _ASM_ARM_EFI_H */
Annotation
- Immediate include surface: `asm/cacheflush.h`, `asm/cachetype.h`, `asm/early_ioremap.h`, `asm/fixmap.h`, `asm/highmem.h`, `asm/mach/map.h`, `asm/mmu_context.h`, `asm/ptrace.h`.
- Detected declarations: `struct efi_arm_entry_state`, `function efi_set_pgd`, `function efi_get_max_initrd_addr`, `function efi_capsule_flush_cache_range`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.