drivers/xen/xenbus/xenbus_probe_backend.c

File Facts

System

Linux kernel

Corpus path

drivers/xen/xenbus/xenbus_probe_backend.c

Extension

.c

Size

8338 bytes

Lines

317

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/kernel.h
• linux/err.h
• linux/string.h
• linux/ctype.h
• linux/fcntl.h
• linux/mm.h
• linux/notifier.h
• linux/export.h
• linux/semaphore.h
• asm/page.h
• asm/xen/hypervisor.h
• asm/hypervisor.h
• xen/xenbus.h
• xen/features.h
• xenbus.h

Detected Declarations

• function file
• function xenbus_uevent_backend
• function xenbus_probe_backend_unit
• function xenbus_probe_backend
• function frontend_will_handle
• function frontend_changed
• function backend_changed
• function read_frontend_details
• function xenbus_dev_is_online
• function __xenbus_register_backend
• function backend_probe_and_watch
• function backend_reclaim_memory
• function backend_shrink_memory_count
• function xenbus_probe_backend_init
• module init xenbus_probe_backend_init
• export xenbus_dev_is_online
• export __xenbus_register_backend

Annotated Snippet

subsys_initcall(xenbus_probe_backend_init);

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/err.h`, `linux/string.h`, `linux/ctype.h`, `linux/fcntl.h`, `linux/mm.h`, `linux/notifier.h`, `linux/export.h`.
• Detected declarations: `function file`, `function xenbus_uevent_backend`, `function xenbus_probe_backend_unit`, `function xenbus_probe_backend`, `function frontend_will_handle`, `function frontend_changed`, `function backend_changed`, `function read_frontend_details`, `function xenbus_dev_is_online`, `function __xenbus_register_backend`.
• Atlas domain: Driver Families / drivers/xen.
• Implementation status: integration implementation candidate.

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.