arch/sh/include/asm/hugetlb.h

File Facts

System

Linux kernel

Corpus path

arch/sh/include/asm/hugetlb.h

Extension

.h

Size

554 bytes

Lines

24

Domain

Architecture Layer

Bucket

arch/sh

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

• asm/cacheflush.h
• asm/page.h
• asm-generic/hugetlb.h

Detected Declarations

• function huge_ptep_clear_flush
• function arch_clear_hugetlb_flags

Annotated Snippet

#ifndef _ASM_SH_HUGETLB_H
#define _ASM_SH_HUGETLB_H

#include <asm/cacheflush.h>
#include <asm/page.h>

#define __HAVE_ARCH_HUGE_PTEP_CLEAR_FLUSH
static inline pte_t huge_ptep_clear_flush(struct vm_area_struct *vma,
					  unsigned long addr, pte_t *ptep)
{
	return *ptep;
}

static inline void arch_clear_hugetlb_flags(struct folio *folio)
{
	clear_bit(PG_dcache_clean, &folio->flags.f);
}
#define arch_clear_hugetlb_flags arch_clear_hugetlb_flags

#include <asm-generic/hugetlb.h>

#endif /* _ASM_SH_HUGETLB_H */

Annotation

• Immediate include surface: `asm/cacheflush.h`, `asm/page.h`, `asm-generic/hugetlb.h`.
• Detected declarations: `function huge_ptep_clear_flush`, `function arch_clear_hugetlb_flags`.
• Atlas domain: Architecture Layer / arch/sh.
• 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.