arch/alpha/include/asm/pgalloc.h

File Facts

System

Linux kernel

Corpus path

arch/alpha/include/asm/pgalloc.h

Extension

.h

Size

761 bytes

Lines

37

Domain

Architecture Layer

Bucket

arch/alpha

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/mm.h
• linux/mmzone.h
• asm-generic/pgalloc.h

Detected Declarations

• function pmd_populate
• function pmd_populate_kernel
• function pud_populate

Annotated Snippet

#ifndef _ALPHA_PGALLOC_H
#define _ALPHA_PGALLOC_H

#include <linux/mm.h>
#include <linux/mmzone.h>

#include <asm-generic/pgalloc.h>

/*      
 * Allocate and free page tables. The xxx_kernel() versions are
 * used to allocate a kernel page table - this turns on ASN bits
 * if any.
 */

static inline void
pmd_populate(struct mm_struct *mm, pmd_t *pmd, pgtable_t pte)
{
	pmd_set(pmd, (pte_t *)(page_to_pa(pte) + PAGE_OFFSET));
}

static inline void
pmd_populate_kernel(struct mm_struct *mm, pmd_t *pmd, pte_t *pte)
{
	pmd_set(pmd, pte);
}

static inline void
pud_populate(struct mm_struct *mm, pud_t *pud, pmd_t *pmd)
{
	pud_set(pud, pmd);
}

extern pgd_t *pgd_alloc(struct mm_struct *mm);

#endif /* _ALPHA_PGALLOC_H */

Annotation

• Immediate include surface: `linux/mm.h`, `linux/mmzone.h`, `asm-generic/pgalloc.h`.
• Detected declarations: `function pmd_populate`, `function pmd_populate_kernel`, `function pud_populate`.
• Atlas domain: Architecture Layer / arch/alpha.
• 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.