drivers/scsi/vmw_pvscsi.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/vmw_pvscsi.c

Extension

.c

Size

44242 bytes

Lines

1622

Domain

Driver Families

Bucket

drivers/scsi

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• 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/kernel.h
• linux/module.h
• linux/interrupt.h
• linux/slab.h
• linux/workqueue.h
• linux/pci.h
• scsi/scsi.h
• scsi/scsi_host.h
• scsi/scsi_cmnd.h
• scsi/scsi_device.h
• scsi/scsi_tcq.h
• vmw_pvscsi.h

Detected Declarations

• struct pvscsi_sg_list
• struct pvscsi_ctx
• struct pvscsi_adapter
• function pvscsi_dev
• function pvscsi_find_context
• function pvscsi_acquire_context
• function pvscsi_release_context
• function pvscsi_map_context
• function pvscsi_get_context
• function pvscsi_reg_write
• function pvscsi_reg_read
• function pvscsi_read_intr_status
• function pvscsi_write_intr_status
• function pvscsi_unmask_intr
• function pvscsi_mask_intr
• function pvscsi_write_cmd_desc
• function pvscsi_abort_cmd
• function pvscsi_kick_rw_io
• function pvscsi_process_request_ring
• function scsi_is_rw
• function pvscsi_kick_io
• function ll_adapter_reset
• function ll_bus_reset
• function ll_device_reset
• function pvscsi_create_sg
• function pvscsi_map_buffers
• function pvscsi_patch_sense
• function pvscsi_unmap_buffers
• function pvscsi_allocate_rings
• function pvscsi_setup_all_rings
• function pvscsi_change_queue_depth
• function pvscsi_complete_request
• function pvscsi_process_completion_ring
• function pvscsi_queue_ring
• function pvscsi_queue_lck
• function DEF_SCSI_QCMD
• function pvscsi_reset_all
• function pvscsi_host_reset
• function pvscsi_bus_reset
• function pvscsi_device_reset
• function pvscsi_process_msg
• function pvscsi_msg_pending
• function pvscsi_process_msg_ring
• function pvscsi_msg_workqueue_handler
• function pvscsi_setup_msg_workqueue
• function pvscsi_setup_req_threshold
• function pvscsi_isr
• function pvscsi_shared_isr

Annotated Snippet

static struct pci_driver pvscsi_pci_driver = {
	.name		= "vmw_pvscsi",
	.id_table	= pvscsi_pci_tbl,
	.probe		= pvscsi_probe,
	.remove		= pvscsi_remove,
	.shutdown       = pvscsi_shutdown,
};

static int __init pvscsi_init(void)
{
	pr_info("%s - version %s\n",
		PVSCSI_LINUX_DRIVER_DESC, PVSCSI_DRIVER_VERSION_STRING);
	return pci_register_driver(&pvscsi_pci_driver);
}

static void __exit pvscsi_exit(void)
{
	pci_unregister_driver(&pvscsi_pci_driver);
}

module_init(pvscsi_init);
module_exit(pvscsi_exit);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/interrupt.h`, `linux/slab.h`, `linux/workqueue.h`, `linux/pci.h`, `scsi/scsi.h`, `scsi/scsi_host.h`.
• Detected declarations: `struct pvscsi_sg_list`, `struct pvscsi_ctx`, `struct pvscsi_adapter`, `function pvscsi_dev`, `function pvscsi_find_context`, `function pvscsi_acquire_context`, `function pvscsi_release_context`, `function pvscsi_map_context`, `function pvscsi_get_context`, `function pvscsi_reg_write`.
• Atlas domain: Driver Families / drivers/scsi.
• Implementation status: pattern 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.