drivers/scsi/xen-scsifront.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/xen-scsifront.c

Extension

.c

Size

31179 bytes

Lines

1239

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/device.h
• linux/wait.h
• linux/interrupt.h
• linux/mutex.h
• linux/spinlock.h
• linux/sched.h
• linux/blkdev.h
• linux/pfn.h
• linux/slab.h
• linux/bitops.h
• scsi/scsi_cmnd.h
• scsi/scsi_device.h
• scsi/scsi.h
• scsi/scsi_host.h
• xen/xen.h
• xen/xenbus.h
• xen/grant_table.h
• xen/events.h
• xen/page.h
• xen/interface/grant_table.h
• xen/interface/io/vscsiif.h
• xen/interface/io/protocols.h
• asm/xen/hypervisor.h

Detected Declarations

• struct vscsifrnt_shadow
• struct vscsifrnt_info
• function scsifront_wake_up
• function scsifront_get_rqid
• function _scsifront_put_rqid
• function scsifront_put_rqid
• function scsifront_do_request
• function scsifront_set_error
• function scsifront_gnttab_done
• function scsifront_host_byte
• function scsifront_cdb_cmd_done
• function scsifront_sync_cmd_done
• function scsifront_do_response
• function scsifront_ring_drain
• function scsifront_cmd_done
• function scsifront_irq_fn
• function scsifront_finish_all
• function map_data_for_request
• function scsi_for_each_sg
• function scsifront_enter
• function scsifront_return
• function scsifront_queuecommand
• function handling
• function scsifront_eh_abort_handler
• function scsifront_dev_reset_handler
• function scsifront_sdev_configure
• function scsifront_sdev_destroy
• function scsifront_alloc_ring
• function scsifront_free_ring
• function scsifront_init_ring
• function scsifront_probe
• function scsifront_resume
• function scsifront_suspend
• function scsifront_remove
• function scsifront_disconnect
• function scsifront_do_lun_hotplug
• function scsifront_read_backend_params
• function scsifront_backend_changed
• function scsifront_init
• function scsifront_exit
• module init scsifront_init

Annotated Snippet

module_init(scsifront_init);

static void __exit scsifront_exit(void)
{
	xenbus_unregister_driver(&scsifront_driver);
}
module_exit(scsifront_exit);

MODULE_DESCRIPTION("Xen SCSI frontend driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("xen:vscsi");
MODULE_AUTHOR("Juergen Gross <jgross@suse.com>");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/device.h`, `linux/wait.h`, `linux/interrupt.h`, `linux/mutex.h`, `linux/spinlock.h`, `linux/sched.h`.
• Detected declarations: `struct vscsifrnt_shadow`, `struct vscsifrnt_info`, `function scsifront_wake_up`, `function scsifront_get_rqid`, `function _scsifront_put_rqid`, `function scsifront_put_rqid`, `function scsifront_do_request`, `function scsifront_set_error`, `function scsifront_gnttab_done`, `function scsifront_host_byte`.
• 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.