arch/mips/include/asm/elfcore-compat.h

File Facts

System

Linux kernel

Corpus path

arch/mips/include/asm/elfcore-compat.h

Extension

.h

Size

841 bytes

Lines

30

Domain

Architecture Layer

Bucket

arch/mips

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 o32_elf_prstatus

Annotated Snippet

#ifndef _ASM_MIPS_ELFCORE_COMPAT_H
#define _ASM_MIPS_ELFCORE_COMPAT_H

/*
 * On mips we have two 32bit ABIs - o32 and n32.  The latter
 * has bigger registers, so we use it for compat_elf_regset_t.
 * The former uses o32_elf_prstatus and PRSTATUS_SIZE/SET_PR_FPVALID
 * are used to choose the size and location of ->pr_fpvalid of
 * the layout actually used.
 */
typedef elf_gregset_t compat_elf_gregset_t;

struct o32_elf_prstatus
{
	struct compat_elf_prstatus_common	common;
	unsigned int 			pr_reg[ELF_NGREG];
	compat_int_t			pr_fpvalid;
};

#define PRSTATUS_SIZE \
	(!test_thread_flag(TIF_32BIT_REGS) \
		? sizeof(struct compat_elf_prstatus) \
		: sizeof(struct o32_elf_prstatus))
#define SET_PR_FPVALID(S) \
	(*(!test_thread_flag(TIF_32BIT_REGS) \
		? &(S)->pr_fpvalid 	\
		: &((struct o32_elf_prstatus *)(S))->pr_fpvalid) = 1)

#endif

Annotation

• Detected declarations: `struct o32_elf_prstatus`.
• Atlas domain: Architecture Layer / arch/mips.
• 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.