drivers/xen/pvcalls-front.c

File Facts

System

Linux kernel

Corpus path

drivers/xen/pvcalls-front.c

Extension

.c

Size

33220 bytes

Lines

1313

Domain

Driver Families

Bucket

drivers/xen

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• 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

• linux/module.h
• linux/net.h
• linux/socket.h
• net/sock.h
• xen/events.h
• xen/grant_table.h
• xen/xen.h
• xen/xenbus.h
• xen/interface/io/pvcalls.h
• pvcalls-front.h

Detected Declarations

• struct pvcalls_bedata
• struct sock_mapping
• function pvcalls_exit_sock
• function get_request
• function pvcalls_front_write_todo
• function pvcalls_front_read_todo
• function pvcalls_front_event_handler
• function pvcalls_front_destroy_active
• function pvcalls_front_free_map
• function pvcalls_front_conn_handler
• function pvcalls_front_socket
• function free_active_ring
• function alloc_active_ring
• function create_active
• function pvcalls_front_connect
• function __write_ring
• function pvcalls_front_sendmsg
• function __read_ring
• function pvcalls_front_recvmsg
• function pvcalls_front_bind
• function pvcalls_front_listen
• function pvcalls_front_accept
• function pvcalls_front_poll_passive
• function pvcalls_front_poll_active
• function pvcalls_front_poll
• function pvcalls_front_release
• function pvcalls_front_remove
• function list_for_each_entry_safe
• function pvcalls_front_probe
• function pvcalls_front_changed
• function pvcalls_frontend_init
• module init pvcalls_frontend_init
• export pvcalls_front_socket
• export pvcalls_front_connect
• export pvcalls_front_sendmsg
• export pvcalls_front_recvmsg
• export pvcalls_front_bind
• export pvcalls_front_listen
• export pvcalls_front_accept
• export pvcalls_front_poll
• export pvcalls_front_release

Annotated Snippet

module_init(pvcalls_frontend_init);

MODULE_DESCRIPTION("Xen PV Calls frontend driver");
MODULE_AUTHOR("Stefano Stabellini <sstabellini@kernel.org>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/net.h`, `linux/socket.h`, `net/sock.h`, `xen/events.h`, `xen/grant_table.h`, `xen/xen.h`, `xen/xenbus.h`.
• Detected declarations: `struct pvcalls_bedata`, `struct sock_mapping`, `function pvcalls_exit_sock`, `function get_request`, `function pvcalls_front_write_todo`, `function pvcalls_front_read_todo`, `function pvcalls_front_event_handler`, `function pvcalls_front_destroy_active`, `function pvcalls_front_free_map`, `function pvcalls_front_conn_handler`.
• Atlas domain: Driver Families / drivers/xen.
• 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.