drivers/scsi/ibmvscsi/ibmvfc.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/ibmvscsi/ibmvfc.c

Extension

.c

Size

188466 bytes

Lines

6608

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/dmapool.h
• linux/delay.h
• linux/interrupt.h
• linux/irqdomain.h
• linux/kthread.h
• linux/slab.h
• linux/of.h
• linux/pm.h
• linux/stringify.h
• linux/bsg-lib.h
• asm/firmware.h
• asm/irq.h
• asm/vio.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_host.h
• scsi/scsi_device.h
• scsi/scsi_tcq.h
• scsi/scsi_transport_fc.h
• scsi/scsi_bsg_fc.h
• ibmvfc.h

Detected Declarations

• function h_reg_sub_crq
• function ibmvfc_check_caps
• function ibmvfc_trc_start
• function ibmvfc_trc_end
• function ibmvfc_get_err_index
• function ibmvfc_get_err_result
• function ibmvfc_retry_cmd
• function ibmvfc_set_tgt_action
• function ibmvfc_set_host_state
• function ibmvfc_set_host_action
• function ibmvfc_reinit_host
• function ibmvfc_del_tgt
• function ibmvfc_link_down
• function ibmvfc_init_host
• function list_for_each_entry
• function ibmvfc_send_crq
• function ibmvfc_send_sub_crq
• function ibmvfc_send_crq_init
• function ibmvfc_send_crq_init_complete
• function ibmvfc_init_event_pool
• function ibmvfc_free_event_pool
• function ibmvfc_free_queue
• function ibmvfc_release_crq_queue
• function ibmvfc_reenable_crq_queue
• function ibmvfc_reset_crq
• function ibmvfc_valid_event
• function ibmvfc_free_event
• function ibmvfc_scsi_eh_done
• function ibmvfc_complete_purge
• function list_for_each_entry_safe
• function ibmvfc_fail_request
• function ibmvfc_purge_requests
• function ibmvfc_hard_reset_host
• function __ibmvfc_reset_host
• function ibmvfc_reset_host
• function ibmvfc_retry_host_init
• function list_for_each_entry
• function ibmvfc_get_host_speed
• function ibmvfc_get_host_port_state
• function ibmvfc_set_rport_dev_loss_tmo
• function ibmvfc_release_tgt
• function ibmvfc_get_starget_node_name
• function ibmvfc_get_starget_port_name
• function ibmvfc_get_starget_port_id
• function ibmvfc_wait_while_resetting
• function ibmvfc_issue_fc_host_lip
• function ibmvfc_gather_partition_info
• function ibmvfc_set_login_info

Annotated Snippet

module_init(ibmvfc_module_init);
module_exit(ibmvfc_module_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/moduleparam.h`, `linux/dma-mapping.h`, `linux/dmapool.h`, `linux/delay.h`, `linux/interrupt.h`, `linux/irqdomain.h`, `linux/kthread.h`.
• Detected declarations: `function h_reg_sub_crq`, `function ibmvfc_check_caps`, `function ibmvfc_trc_start`, `function ibmvfc_trc_end`, `function ibmvfc_get_err_index`, `function ibmvfc_get_err_result`, `function ibmvfc_retry_cmd`, `function ibmvfc_set_tgt_action`, `function ibmvfc_set_host_state`, `function ibmvfc_set_host_action`.
• 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.