drivers/xen/xen-scsiback.c

File Facts

System

Linux kernel

Corpus path

drivers/xen/xen-scsiback.c

Extension

.c

Size

48475 bytes

Lines

1892

Domain

Driver Families

Bucket

drivers/xen

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/utsname.h
• linux/interrupt.h
• linux/slab.h
• linux/wait.h
• linux/sched.h
• linux/list.h
• linux/gfp.h
• linux/delay.h
• linux/spinlock.h
• linux/configfs.h
• generated/utsrelease.h
• scsi/scsi_host.h
• target/target_core_base.h
• target/target_core_fabric.h
• asm/hypervisor.h
• xen/xen.h
• xen/balloon.h
• xen/events.h
• xen/xenbus.h
• xen/grant_table.h
• xen/page.h
• xen/interface/grant_table.h
• xen/interface/io/vscsiif.h

Detected Declarations

• struct ids_tuple
• struct v2p_entry
• struct vscsibk_info
• struct vscsibk_pend
• struct scsiback_nexus
• struct scsiback_tport
• struct scsiback_tpg
• function scsiback_get
• function scsiback_put
• function vaddr_page
• function vaddr
• function scsiback_print_status
• function scsiback_fast_flush_area
• function scsiback_free_translation_entry
• function scsiback_result
• function scsiback_send_response
• function scsiback_do_resp_with_sense
• function scsiback_cmd_done
• function scsiback_cmd_exec
• function scsiback_gnttab_data_map_batch
• function scsiback_gnttab_data_map_list
• function scsiback_gnttab_data_map
• function for_each_sg
• function scsiback_disconnect
• function scsiback_device_action
• function scsiback_do_cmd_fn
• function scsiback_irq_fn
• function scsiback_init_sring
• function scsiback_map
• function scsiback_add_translation_entry
• function hlist_for_each_entry
• function scsiback_del_translation_entry
• function scsiback_do_add_lun
• function scsiback_do_del_lun
• function scsiback_do_1lun_hotplug
• function scsiback_do_lun_hotplug
• function scsiback_frontend_changed
• function scsiback_release_translation_entry
• function list_for_each_entry_safe
• function scsiback_remove
• function scsiback_probe
• function scsiback_get_tag
• function scsiback_make_tport
• function scsiback_drop_tport
• function scsiback_check_stop_free
• function scsiback_release_cmd
• function scsiback_write_pending
• function scsiback_queue_data_in

Annotated Snippet

module_init(scsiback_init);
module_exit(scsiback_exit);

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

Annotation

• Immediate include surface: `linux/module.h`, `linux/utsname.h`, `linux/interrupt.h`, `linux/slab.h`, `linux/wait.h`, `linux/sched.h`, `linux/list.h`, `linux/gfp.h`.
• Detected declarations: `struct ids_tuple`, `struct v2p_entry`, `struct vscsibk_info`, `struct vscsibk_pend`, `struct scsiback_nexus`, `struct scsiback_tport`, `struct scsiback_tpg`, `function scsiback_get`, `function scsiback_put`, `function vaddr_page`.
• Atlas domain: Driver Families / drivers/xen.
• 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.