drivers/scsi/storvsc_drv.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/storvsc_drv.c

Extension

.c

Size

61115 bytes

Lines

2259

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.
• 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/kernel.h
• linux/wait.h
• linux/sched.h
• linux/completion.h
• linux/string.h
• linux/mm.h
• linux/delay.h
• linux/init.h
• linux/slab.h
• linux/module.h
• linux/device.h
• linux/hyperv.h
• linux/blkdev.h
• linux/dma-mapping.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_host.h
• scsi/scsi_device.h
• scsi/scsi_tcq.h
• scsi/scsi_eh.h
• scsi/scsi_devinfo.h
• scsi/scsi_dbg.h
• scsi/scsi_transport_fc.h
• scsi/scsi_transport.h

Detected Declarations

• struct hv_fc_wwn_packet
• struct vmscsi_request
• struct vmstorage_channel_properties
• struct vmstorage_protocol_version
• struct vstor_packet
• struct storvsc_cmd_request
• struct storvsc_device
• struct hv_host_device
• struct storvsc_scan_work
• enum vstor_packet_operation
• enum storvsc_request_type
• function do_logging
• function storvsc_device_scan
• function storvsc_host_scan
• function storvsc_remove_lun
• function storvsc_wait_to_drain
• function storvsc_change_target_cpu
• function storvsc_next_request_id
• function handle_sc_creation
• function handle_multichannel_storage
• function cache_wwn
• function storvsc_execute_vstor_op
• function storvsc_channel_init
• function storvsc_handle_error
• function scsi_report_sense
• function storvsc_command_completion
• function and
• function storvsc_on_io_completion
• function storvsc_on_receive
• function storvsc_on_channel_callback
• function foreach_vmbus_pkt
• function storvsc_connect_to_vsp
• function storvsc_dev_remove
• function for_each_cpu
• function storvsc_do_io
• function for_each_cpu_wrap
• function for_each_cpu_wrap
• function storvsc_device_alloc
• function storvsc_sdev_configure
• function storvsc_get_chs
• function storvsc_host_reset_handler
• function storvsc_eh_timed_out
• function storvsc_scsi_cmd_ok
• function storvsc_queuecommand
• function for_each_sg
• function hv_dev_is_fc
• function storvsc_probe
• function storvsc_change_queue_depth

Annotated Snippet

module_init(storvsc_drv_init);
module_exit(storvsc_drv_exit);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/wait.h`, `linux/sched.h`, `linux/completion.h`, `linux/string.h`, `linux/mm.h`, `linux/delay.h`, `linux/init.h`.
• Detected declarations: `struct hv_fc_wwn_packet`, `struct vmscsi_request`, `struct vmstorage_channel_properties`, `struct vmstorage_protocol_version`, `struct vstor_packet`, `struct storvsc_cmd_request`, `struct storvsc_device`, `struct hv_host_device`, `struct storvsc_scan_work`, `enum vstor_packet_operation`.
• 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.

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.