arch/um/drivers/virtio_uml.c

File Facts

System

Linux kernel

Corpus path

arch/um/drivers/virtio_uml.c

Extension

.c

Size

38071 bytes

Lines

1545

Domain

Architecture Layer

Bucket

arch/um

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration 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.
• 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/of.h
• linux/platform_device.h
• linux/slab.h
• linux/string_choices.h
• linux/virtio.h
• linux/virtio_config.h
• linux/virtio_ring.h
• linux/time-internal.h
• linux/virtio-uml.h
• shared/as-layout.h
• irq_kern.h
• init.h
• os.h
• mconsole_kern.h
• vhost_user.h

Detected Declarations

• struct virtio_uml_platform_data
• struct virtio_uml_device
• struct virtio_uml_vq_info
• function full_sendmsg_fds
• function full_read
• function vhost_user_recv_header
• function vhost_user_recv
• function vhost_user_check_reset
• function vhost_user_recv_resp
• function vhost_user_recv_u64
• function vhost_user_recv_req
• function vhost_user_send
• function vhost_user_send_no_payload
• function vhost_user_send_no_payload_fd
• function vhost_user_send_u64
• function vhost_user_set_owner
• function vhost_user_get_features
• function vhost_user_set_features
• function vhost_user_get_protocol_features
• function vhost_user_set_protocol_features
• function vhost_user_get_queue_num
• function vhost_user_reply
• function vu_req_read_message
• function virtio_device_for_each_vq
• function vu_req_interrupt
• function virtio_device_for_each_vq
• function vu_req_interrupt_comm_handler
• function vhost_user_init_slave_req
• function vhost_user_init
• function vhost_user_get_config
• function vhost_user_set_config
• function vhost_user_init_mem_region
• function vhost_user_set_mem_table
• function vhost_user_set_vring_state
• function vhost_user_set_vring_num
• function vhost_user_set_vring_base
• function vhost_user_set_vring_addr
• function vhost_user_set_vring_fd
• function vhost_user_set_vring_call
• function vhost_user_set_vring_kick
• function vhost_user_set_vring_enable
• function vu_notify
• function vu_interrupt
• function vu_get
• function vu_set
• function vu_get_status
• function vu_set_status
• function vu_reset

Annotated Snippet

module_init(virtio_uml_init);
module_exit(virtio_uml_exit);
__uml_exitcall(virtio_uml_exit);

MODULE_DESCRIPTION("UML driver for vhost-user virtio devices");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/of.h`, `linux/platform_device.h`, `linux/slab.h`, `linux/string_choices.h`, `linux/virtio.h`, `linux/virtio_config.h`, `linux/virtio_ring.h`.
• Detected declarations: `struct virtio_uml_platform_data`, `struct virtio_uml_device`, `struct virtio_uml_vq_info`, `function full_sendmsg_fds`, `function full_read`, `function vhost_user_recv_header`, `function vhost_user_recv`, `function vhost_user_check_reset`, `function vhost_user_recv_resp`, `function vhost_user_recv_u64`.
• Atlas domain: Architecture Layer / arch/um.
• 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.