net/9p/trans_xen.c

File Facts

System

Linux kernel

Corpus path

net/9p/trans_xen.c

Extension

.c

Size

14421 bytes

Lines

608

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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

• xen/events.h
• xen/grant_table.h
• xen/xen.h
• xen/xenbus.h
• xen/interface/io/9pfs.h
• linux/module.h
• linux/spinlock.h
• linux/fs_context.h
• net/9p/9p.h
• net/9p/client.h
• net/9p/transport.h

Detected Declarations

• struct xen_9pfs_header
• struct xen_9pfs_dataring
• struct xen_9pfs_front_priv
• function p9_xen_cancel
• function p9_xen_create
• function p9_xen_close
• function p9_xen_write_todo
• function p9_xen_request
• function p9_xen_response
• function xen_9pfs_front_event_handler
• function xen_9pfs_front_free
• function xen_9pfs_front_remove
• function xen_9pfs_front_alloc_dataring
• function xen_9pfs_front_init
• function xen_9pfs_front_probe
• function xen_9pfs_front_resume
• function xen_9pfs_front_changed
• function p9_trans_xen_init
• function p9_trans_xen_exit
• module init p9_trans_xen_init

Annotated Snippet

module_init(p9_trans_xen_init);
MODULE_ALIAS_9P("xen");

static void __exit p9_trans_xen_exit(void)
{
	v9fs_unregister_trans(&p9_xen_trans);
	return xenbus_unregister_driver(&xen_9pfs_front_driver);
}
module_exit(p9_trans_xen_exit);

MODULE_ALIAS("xen:9pfs");
MODULE_AUTHOR("Stefano Stabellini <stefano@aporeto.com>");
MODULE_DESCRIPTION("Xen Transport for 9P");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `xen/events.h`, `xen/grant_table.h`, `xen/xen.h`, `xen/xenbus.h`, `xen/interface/io/9pfs.h`, `linux/module.h`, `linux/spinlock.h`, `linux/fs_context.h`.
• Detected declarations: `struct xen_9pfs_header`, `struct xen_9pfs_dataring`, `struct xen_9pfs_front_priv`, `function p9_xen_cancel`, `function p9_xen_create`, `function p9_xen_close`, `function p9_xen_write_todo`, `function p9_xen_request`, `function p9_xen_response`, `function xen_9pfs_front_event_handler`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.