arch/sh/include/asm/tlb.h
Source file repositories/reference/linux-study-clean/arch/sh/include/asm/tlb.h
File Facts
- System
- Linux kernel
- Corpus path
arch/sh/include/asm/tlb.h- Extension
.h- Size
- 740 bytes
- Lines
- 34
- 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
linux/pagemap.hasm-generic/tlb.hlinux/swap.h
Detected Declarations
function tlb_wire_entryfunction tlb_unwire_entry
Annotated Snippet
#ifndef __ASM_SH_TLB_H
#define __ASM_SH_TLB_H
#ifndef __ASSEMBLER__
#include <linux/pagemap.h>
#include <asm-generic/tlb.h>
#ifdef CONFIG_MMU
#include <linux/swap.h>
#if defined(CONFIG_CPU_SH4)
extern void tlb_wire_entry(struct vm_area_struct *, unsigned long, pte_t);
extern void tlb_unwire_entry(void);
#else
static inline void tlb_wire_entry(struct vm_area_struct *vma ,
unsigned long addr, pte_t pte)
{
BUG();
}
static inline void tlb_unwire_entry(void)
{
BUG();
}
#endif /* CONFIG_CPU_SH4 */
asmlinkage int handle_tlbmiss(struct pt_regs *regs, unsigned long error_code,
unsigned long address);
#endif /* CONFIG_MMU */
#endif /* __ASSEMBLER__ */
#endif /* __ASM_SH_TLB_H */
Annotation
- Immediate include surface: `linux/pagemap.h`, `asm-generic/tlb.h`, `linux/swap.h`.
- Detected declarations: `function tlb_wire_entry`, `function tlb_unwire_entry`.
- 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.