arch/um/include/asm/mmu_context.h

File Facts

System

Linux kernel

Corpus path

arch/um/include/asm/mmu_context.h

Extension

.h

Size

680 bytes

Lines

30

Domain

Architecture Layer

Bucket

arch/um

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/sched.h
• linux/mm_types.h
• linux/mmap_lock.h
• asm/mm_hooks.h
• asm/mmu.h
• asm-generic/mmu_context.h

Detected Declarations

• function Copyright

Annotated Snippet

#ifndef __UM_MMU_CONTEXT_H
#define __UM_MMU_CONTEXT_H

#include <linux/sched.h>
#include <linux/mm_types.h>
#include <linux/mmap_lock.h>

#include <asm/mm_hooks.h>
#include <asm/mmu.h>

static inline void switch_mm(struct mm_struct *prev, struct mm_struct *next, 
			     struct task_struct *tsk)
{
}

#define init_new_context init_new_context
extern int init_new_context(struct task_struct *task, struct mm_struct *mm);

#define destroy_context destroy_context
extern void destroy_context(struct mm_struct *mm);

#include <asm-generic/mmu_context.h>

#endif

Annotation

• Immediate include surface: `linux/sched.h`, `linux/mm_types.h`, `linux/mmap_lock.h`, `asm/mm_hooks.h`, `asm/mmu.h`, `asm-generic/mmu_context.h`.
• Detected declarations: `function Copyright`.
• Atlas domain: Architecture Layer / arch/um.
• 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.