drivers/xen/xenfs/xenstored.c
Source file repositories/reference/linux-study-clean/drivers/xen/xenfs/xenstored.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/xen/xenfs/xenstored.c- Extension
.c- Size
- 1555 bytes
- Lines
- 70
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/slab.hlinux/types.hlinux/mm.hlinux/fs.hxen/page.hxen/xenbus.hxenfs.h
Detected Declarations
function xsd_readfunction xsd_releasefunction xsd_kva_openfunction xsd_kva_mmapfunction xsd_port_open
Annotated Snippet
const struct file_operations xsd_kva_file_ops = {
.open = xsd_kva_open,
.mmap = xsd_kva_mmap,
.read = xsd_read,
.release = xsd_release,
};
static int xsd_port_open(struct inode *inode, struct file *file)
{
file->private_data = (void *)kasprintf(GFP_KERNEL, "%d",
xen_store_evtchn);
if (!file->private_data)
return -ENOMEM;
return 0;
}
const struct file_operations xsd_port_file_ops = {
.open = xsd_port_open,
.read = xsd_read,
.release = xsd_release,
};
Annotation
- Immediate include surface: `linux/slab.h`, `linux/types.h`, `linux/mm.h`, `linux/fs.h`, `xen/page.h`, `xen/xenbus.h`, `xenfs.h`.
- Detected declarations: `function xsd_read`, `function xsd_release`, `function xsd_kva_open`, `function xsd_kva_mmap`, `function xsd_port_open`.
- 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.