drivers/xen/xenbus/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/xen/xenbus/Makefile

Extension

[no extension]

Size

359 bytes

Lines

14

Domain

Driver Families

Bucket

drivers/xen

Inferred role

Driver Families: build/configuration rule

Status

atlas-only

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.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0
obj-y	+= xenbus.o

xenbus-y := xenbus_client.o
xenbus-y += xenbus_comms.o
xenbus-y += xenbus_xs.o
xenbus-y += xenbus_probe.o

xenbus-$(CONFIG_XEN_BACKEND) += xenbus_probe_backend.o

obj-y	+= xenbus_dev_frontend.o
obj-$(CONFIG_XEN_BACKEND) += xenbus_dev_backend.o
obj-$(CONFIG_XEN_XENBUS_FRONTEND) += xenbus_probe_frontend.o

Annotation

• Atlas domain: Driver Families / drivers/xen.
• Implementation status: atlas-only.

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.