arch/loongarch/include/asm/image.h
Source file repositories/reference/linux-study-clean/arch/loongarch/include/asm/image.h
File Facts
- System
- Linux kernel
- Corpus path
arch/loongarch/include/asm/image.h- Extension
.h- Size
- 1205 bytes
- Lines
- 53
- Domain
- Architecture Layer
- Bucket
- arch/loongarch
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct loongarch_image_headerfunction true
Annotated Snippet
struct loongarch_image_header {
uint8_t dos_sig[2];
uint16_t padding_1[3];
uint64_t kernel_entry;
uint64_t kernel_asize;
uint64_t text_offset;
uint32_t padding_2[7];
uint32_t pe_header;
};
/*
* loongarch_header_check_dos_sig - Helper to check the header
*
* Returns true (non-zero) if 'MZ' signature is found.
*/
static inline int loongarch_header_check_dos_sig(const struct loongarch_image_header *h)
{
if (!h)
return 0;
return (h->dos_sig[0] == 'M' && h->dos_sig[1] == 'Z');
}
#endif /* __ASSEMBLER__ */
#endif /* __ASM_IMAGE_H */
Annotation
- Detected declarations: `struct loongarch_image_header`, `function true`.
- Atlas domain: Architecture Layer / arch/loongarch.
- 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.