drivers/scsi/virtio_scsi.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/virtio_scsi.c

Extension

.c

Size

29183 bytes

Lines

1107

Domain

Driver Families

Bucket

drivers/scsi

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/slab.h
• linux/mempool.h
• linux/interrupt.h
• linux/virtio.h
• linux/virtio_ids.h
• linux/virtio_config.h
• linux/virtio_scsi.h
• linux/cpu.h
• linux/blkdev.h
• linux/blk-integrity.h
• scsi/scsi_host.h
• scsi/scsi_device.h
• scsi/scsi_cmnd.h
• scsi/scsi_tcq.h
• scsi/scsi_devinfo.h
• linux/seqlock.h
• linux/dma-mapping.h
• sd.h

Detected Declarations

• struct virtio_scsi_cmd
• struct virtio_scsi_event_node
• struct virtio_scsi_vq
• struct virtio_scsi
• function virtscsi_compute_resid
• function virtscsi_complete_cmd
• function virtscsi_vq_done
• function virtscsi_req_done
• function virtscsi_poll_requests
• function virtscsi_complete_free
• function virtscsi_ctrl_done
• function virtscsi_kick_event
• function virtscsi_kick_event_all
• function virtscsi_cancel_event_work
• function virtscsi_handle_transport_reset
• function virtscsi_handle_param_change
• function virtscsi_rescan_hotunplug
• function shost_for_each_device
• function virtscsi_handle_event
• function virtscsi_complete_event
• function virtscsi_event_done
• function __virtscsi_add_cmd
• function virtscsi_kick_vq
• function virtscsi_add_cmd
• function virtio_scsi_init_hdr
• function virtio_scsi_init_hdr_pi
• function virtscsi_queuecommand
• function virtscsi_tmf
• function virtscsi_device_reset
• function virtscsi_device_alloc
• function virtscsi_change_queue_depth
• function virtscsi_abort
• function virtscsi_map_queues
• function virtscsi_mq_poll
• function virtscsi_commit_rqs
• function virtscsi_eh_timed_out
• function virtscsi_init_vq
• function virtscsi_remove_vqs
• function virtscsi_init
• function virtscsi_probe
• function virtscsi_remove
• function virtscsi_freeze
• function virtscsi_restore
• function virtio_scsi_init
• function virtio_scsi_fini
• module init virtio_scsi_init

Annotated Snippet

module_init(virtio_scsi_init);
module_exit(virtio_scsi_fini);

MODULE_DEVICE_TABLE(virtio, id_table);
MODULE_DESCRIPTION("Virtio SCSI HBA driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/slab.h`, `linux/mempool.h`, `linux/interrupt.h`, `linux/virtio.h`, `linux/virtio_ids.h`, `linux/virtio_config.h`, `linux/virtio_scsi.h`.
• Detected declarations: `struct virtio_scsi_cmd`, `struct virtio_scsi_event_node`, `struct virtio_scsi_vq`, `struct virtio_scsi`, `function virtscsi_compute_resid`, `function virtscsi_complete_cmd`, `function virtscsi_vq_done`, `function virtscsi_req_done`, `function virtscsi_poll_requests`, `function virtscsi_complete_free`.
• Atlas domain: Driver Families / drivers/scsi.
• 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.