arch/mips/kernel/access-helper.h

File Facts

System

Linux kernel

Corpus path

arch/mips/kernel/access-helper.h

Extension

.h

Size

514 bytes

Lines

20

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.

Dependency Surface

• linux/uaccess.h

Detected Declarations

• function __get_addr
• function __get_inst16
• function __get_inst32

Annotated Snippet

#include <linux/uaccess.h>

static inline int __get_addr(unsigned long *a, unsigned long *p, bool user)
{
	return user ? get_user(*a, (unsigned long __user *)p) :
		      get_kernel_nofault(*a, p);
}

static inline int __get_inst16(u16 *i, u16 *p, bool user)
{
	return user ? get_user(*i, (u16 __user *)p) : get_kernel_nofault(*i, p);
}

static inline int __get_inst32(u32 *i, u32 *p, bool user)
{
	return user ? get_user(*i, (u32 __user *)p) : get_kernel_nofault(*i, p);
}

Annotation

• Immediate include surface: `linux/uaccess.h`.
• Detected declarations: `function __get_addr`, `function __get_inst16`, `function __get_inst32`.
• Atlas domain: Architecture Layer / arch/mips.
• Implementation status: source implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.

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.