drivers/s390/virtio/virtio_ccw.c

File Facts

System

Linux kernel

Corpus path

drivers/s390/virtio/virtio_ccw.c

Extension

.c

Size

40761 bytes

Lines

1584

Domain

Driver Families

Bucket

drivers/s390

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.
• 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_stat.h
• linux/hex.h
• linux/init.h
• linux/memblock.h
• linux/err.h
• linux/virtio.h
• linux/virtio_config.h
• linux/slab.h
• linux/interrupt.h
• linux/virtio_ring.h
• linux/pfn.h
• linux/async.h
• linux/wait.h
• linux/list.h
• linux/bitops.h
• linux/moduleparam.h
• linux/io.h
• linux/kvm_para.h
• linux/notifier.h
• asm/diag.h
• asm/setup.h
• asm/irq.h
• asm/cio.h
• asm/ccwdev.h
• asm/virtio-ccw.h
• asm/isc.h
• asm/airq.h
• asm/tpi.h

Detected Declarations

• struct vq_config_block
• struct vcdev_dma_area
• struct virtio_ccw_device
• struct vq_info_block_legacy
• struct vq_info_block
• struct virtio_feature_desc
• struct virtio_thinint_area
• struct virtio_rev_info
• struct virtio_ccw_vq_info
• struct airq_info
• function indicators_dma
• function indicators2_dma
• function config_block_dma
• function status_dma
• function get_summary_indicator_dma
• function drop_airq_indicator
• function virtio_airq_handler
• function virtio_ccw_drop_indicators
• function doing_io
• function ccw_io_helper
• function virtio_ccw_drop_indicator
• function virtio_ccw_do_kvm_notify
• function virtio_ccw_kvm_notify
• function virtio_ccw_kvm_notify_with_data
• function virtio_ccw_read_vq_conf
• function virtio_ccw_del_vq
• function virtio_ccw_del_vqs
• function virtio_ccw_register_adapter_ind
• function virtio_ccw_find_vqs
• function virtio_ccw_reset
• function virtio_ccw_get_features
• function ccw_transport_features
• function virtio_ccw_get_config
• function virtio_ccw_set_config
• function virtio_ccw_get_status
• function virtio_ccw_set_status
• function virtio_ccw_synchronize_cbs
• function virtio_ccw_release_dev
• function irb_is_error
• function virtio_ccw_check_activity
• function virtio_ccw_int_handler
• function virtio_ccw_check_autoonline
• function virtio_ccw_auto_online
• function virtio_ccw_probe
• function virtio_ccw_remove
• function virtio_ccw_offline
• function virtio_ccw_set_transport_rev
• function virtio_ccw_online

Annotated Snippet

device_initcall(virtio_ccw_init);

Annotation

• Immediate include surface: `linux/kernel_stat.h`, `linux/hex.h`, `linux/init.h`, `linux/memblock.h`, `linux/err.h`, `linux/virtio.h`, `linux/virtio_config.h`, `linux/slab.h`.
• Detected declarations: `struct vq_config_block`, `struct vcdev_dma_area`, `struct virtio_ccw_device`, `struct vq_info_block_legacy`, `struct vq_info_block`, `struct virtio_feature_desc`, `struct virtio_thinint_area`, `struct virtio_rev_info`, `struct virtio_ccw_vq_info`, `struct airq_info`.
• Atlas domain: Driver Families / drivers/s390.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.