drivers/xen/xenfs/xensyms.c

File Facts

System

Linux kernel

Corpus path

drivers/xen/xenfs/xensyms.c

Extension

.c

Size

3116 bytes

Lines

153

Domain

Driver Families

Bucket

drivers/xen

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/init.h
• linux/seq_file.h
• linux/fs.h
• linux/mm.h
• linux/proc_fs.h
• linux/slab.h
• xen/interface/platform.h
• asm/xen/hypercall.h
• xen/xen-ops.h
• xenfs.h

Detected Declarations

• struct xensyms
• function xensyms_next_sym
• function xensyms_show
• function xensyms_stop
• function xensyms_open
• function xensyms_release

Annotated Snippet

const struct file_operations xensyms_ops = {
	.open = xensyms_open,
	.read = seq_read,
	.llseek = seq_lseek,
	.release = xensyms_release
};

Annotation

• Immediate include surface: `linux/init.h`, `linux/seq_file.h`, `linux/fs.h`, `linux/mm.h`, `linux/proc_fs.h`, `linux/slab.h`, `xen/interface/platform.h`, `asm/xen/hypercall.h`.
• Detected declarations: `struct xensyms`, `function xensyms_next_sym`, `function xensyms_show`, `function xensyms_stop`, `function xensyms_open`, `function xensyms_release`.
• Atlas domain: Driver Families / drivers/xen.
• 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.