drivers/virt/acrn/Kconfig
Source file repositories/reference/linux-study-clean/drivers/virt/acrn/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/virt/acrn/Kconfig- Extension
[no extension]- Size
- 577 bytes
- Lines
- 16
- Domain
- Driver Families
- Bucket
- drivers/virt
- 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
config ACRN_HSM
tristate "ACRN Hypervisor Service Module"
depends on ACRN_GUEST
select EVENTFD
help
ACRN Hypervisor Service Module (HSM) is a kernel module which
communicates with ACRN userspace through ioctls and talks to
the ACRN Hypervisor through hypercalls. HSM will only run in
a privileged management VM, called Service VM, to manage User
VMs and do I/O emulation. Not required for simply running
under ACRN as a User VM.
To compile as a module, choose M, the module will be called
acrn. If unsure, say N.
Annotation
- Atlas domain: Driver Families / drivers/virt.
- 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.