drivers/scsi/ibmvscsi/ibmvscsi.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/ibmvscsi/ibmvscsi.c

Extension

.c

Size

71838 bytes

Lines

2439

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/moduleparam.h
• linux/dma-mapping.h
• linux/delay.h
• linux/slab.h
• linux/of.h
• linux/pm.h
• linux/kthread.h
• asm/firmware.h
• asm/vio.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_host.h
• scsi/scsi_device.h
• scsi/scsi_transport_srp.h
• ibmvscsi.h

Detected Declarations

• function ibmvscsi_handle_event
• function ibmvscsi_release_crq_queue
• function ibmvscsi_send_crq
• function ibmvscsi_task
• function gather_partition_info
• function set_adapter_info
• function ibmvscsi_reset_crq_queue
• function ibmvscsi_init_crq_queue
• function ibmvscsi_reenable_crq_queue
• function initialize_event_pool
• function release_event_pool
• function valid_event_struct
• function free_event_struct
• function get_event_struct
• function init_event_struct
• function set_srp_direction
• function unmap_cmd_data
• function map_sg_list
• function scsi_for_each_sg
• function map_data_for_srp_cmd
• function scsi_cmd_to_srp_cmd
• function purge_requests
• function ibmvscsi_set_request_limit
• function ibmvscsi_reset_host
• function ibmvscsi_timeout
• function ibmvscsi_send_crq
• function requests
• function list_for_each_entry
• function event
• function ibmvscsi_handle_crq
• function lun_from_dev
• function ibmvscsi_queuecommand_lck
• function DEF_SCSI_QCMD
• function unmap_persist_bufs
• function ibmvscsi_handle_crq
• function send_srp_login
• function capabilities_rsp
• function send_mad_capabilities
• function ibmvscsi_handle_crq
• function enable_fast_fail
• function ibmvscsi_handle_crq
• function send_mad_adapter_info
• function init_adapter
• function sync_completion
• function ibmvscsi_eh_abort_handler
• function list_for_each_entry
• function ibmvscsi_eh_device_reset_handler
• function ibmvscsi_eh_host_reset_handler

Annotated Snippet

module_init(ibmvscsi_module_init);
module_exit(ibmvscsi_module_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/dma-mapping.h`, `linux/delay.h`, `linux/slab.h`, `linux/of.h`, `linux/pm.h`, `linux/kthread.h`.
• Detected declarations: `function ibmvscsi_handle_event`, `function ibmvscsi_release_crq_queue`, `function ibmvscsi_send_crq`, `function ibmvscsi_task`, `function gather_partition_info`, `function set_adapter_info`, `function ibmvscsi_reset_crq_queue`, `function ibmvscsi_init_crq_queue`, `function ibmvscsi_reenable_crq_queue`, `function initialize_event_pool`.
• 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.