arch/sh/mm/tlb-debugfs.c

File Facts

System

Linux kernel

Corpus path

arch/sh/mm/tlb-debugfs.c

Extension

.c

Size

3742 bytes

Lines

161

Domain

Architecture Layer

Bucket

arch/sh

Inferred role

Architecture Layer: operation-table or driver-model contract

Status

pattern 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 an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/module.h
• linux/debugfs.h
• linux/seq_file.h
• asm/processor.h
• asm/mmu_context.h
• asm/tlbflush.h

Detected Declarations

• enum tlb_type
• function tlb_seq_show
• function tlb_debugfs_open
• function tlb_debugfs_init
• module init tlb_debugfs_init

Annotated Snippet

static const struct file_operations tlb_debugfs_fops = {
	.owner		= THIS_MODULE,
	.open		= tlb_debugfs_open,
	.read		= seq_read,
	.llseek		= seq_lseek,
	.release	= single_release,
};

static int __init tlb_debugfs_init(void)
{
	debugfs_create_file("itlb", S_IRUSR, arch_debugfs_dir,
			    (void *)TLB_TYPE_ITLB, &tlb_debugfs_fops);
	debugfs_create_file("utlb", S_IRUSR, arch_debugfs_dir,
			    (void *)TLB_TYPE_UTLB, &tlb_debugfs_fops);
	return 0;
}
module_init(tlb_debugfs_init);

MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/init.h`, `linux/module.h`, `linux/debugfs.h`, `linux/seq_file.h`, `asm/processor.h`, `asm/mmu_context.h`, `asm/tlbflush.h`.
• Detected declarations: `enum tlb_type`, `function tlb_seq_show`, `function tlb_debugfs_open`, `function tlb_debugfs_init`, `module init tlb_debugfs_init`.
• Atlas domain: Architecture Layer / arch/sh.
• Implementation status: pattern 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.