drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/ibmvscsi_tgt/ibmvscsi_tgt.c

Extension

.c

Size

108964 bytes

Lines

4072

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/kernel.h
• linux/slab.h
• linux/types.h
• linux/list.h
• linux/string.h
• linux/delay.h
• linux/of.h
• target/target_core_base.h
• target/target_core_fabric.h
• asm/hvcall.h
• asm/vio.h
• scsi/viosrp.h
• ibmvscsi_tgt.h

Detected Declarations

• struct port_id
• function ibmvscsis_determine_resid
• function connection_broken
• function ibmvscsis_unregister_command_q
• function ibmvscsis_delete_client_info
• function ibmvscsis_free_command_q
• function ibmvscsis_cmd_q_dequeue
• function ibmvscsis_send_init_message
• function ibmvscsis_check_init_msg
• function ibmvscsis_disconnect
• function ibmvscsis_post_disconnect
• function ibmvscsis_handle_init_compl_msg
• function ibmvscsis_handle_init_msg
• function ibmvscsis_init_msg
• function ibmvscsis_establish_new_q
• function ibmvscsis_reset_queue
• function ibmvscsis_free_cmd_resources
• function ibmvscsis_ready_for_suspend
• function ibmvscsis_trans_event
• function ibmvscsis_poll_cmd_q
• function ibmvscsis_free_cmd_qs
• function list_for_each_entry_safe
• function ibmvscsis_get_free_cmd
• function ibmvscsis_adapter_idle
• function flag
• function ibmvscsis_copy_crq_packet
• function ibmvscsis_adapter_info
• function ibmvscsis_cap_mad
• function ibmvscsis_process_mad
• function srp_snd_msg_failed
• function ibmvscsis_send_messages
• function list_for_each_entry_safe
• function ibmvscsis_send_mad_resp
• function ibmvscsis_mad
• function ibmvscsis_login_rsp
• function ibmvscsis_srp_login_rej
• function ibmvscsis_make_nexus
• function ibmvscsis_drop_nexus
• function ibmvscsis_srp_login
• function ibmvscsis_srp_i_logout
• function ibmvscsis_srp_cmd
• function ibmvscsis_ping_response
• function ibmvscsis_parse_command
• function read_dma_window
• function ibmvscsis_parse_cmd
• function ibmvscsis_parse_task
• function ibmvscsis_scheduler
• function ibmvscsis_alloc_cmds

Annotated Snippet

module_init(ibmvscsis_init);
module_exit(ibmvscsis_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/slab.h`, `linux/types.h`, `linux/list.h`, `linux/string.h`, `linux/delay.h`, `linux/of.h`.
• Detected declarations: `struct port_id`, `function ibmvscsis_determine_resid`, `function connection_broken`, `function ibmvscsis_unregister_command_q`, `function ibmvscsis_delete_client_info`, `function ibmvscsis_free_command_q`, `function ibmvscsis_cmd_q_dequeue`, `function ibmvscsis_send_init_message`, `function ibmvscsis_check_init_msg`, `function ibmvscsis_disconnect`.
• 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.