drivers/virtio/virtio_anchor.c
Source file repositories/reference/linux-study-clean/drivers/virtio/virtio_anchor.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/virtio/virtio_anchor.c- Extension
.c- Size
- 464 bytes
- Lines
- 19
- Domain
- Driver Families
- Bucket
- drivers/virtio
- 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/virtio.hlinux/virtio_anchor.h
Detected Declarations
function virtio_require_restricted_mem_accfunction virtio_no_restricted_mem_accexport virtio_require_restricted_mem_accexport virtio_check_mem_acc_cb
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
#include <linux/virtio.h>
#include <linux/virtio_anchor.h>
bool virtio_require_restricted_mem_acc(struct virtio_device *dev)
{
return true;
}
EXPORT_SYMBOL_GPL(virtio_require_restricted_mem_acc);
static bool virtio_no_restricted_mem_acc(struct virtio_device *dev)
{
return false;
}
bool (*virtio_check_mem_acc_cb)(struct virtio_device *dev) =
virtio_no_restricted_mem_acc;
EXPORT_SYMBOL_GPL(virtio_check_mem_acc_cb);
Annotation
- Immediate include surface: `linux/virtio.h`, `linux/virtio_anchor.h`.
- Detected declarations: `function virtio_require_restricted_mem_acc`, `function virtio_no_restricted_mem_acc`, `export virtio_require_restricted_mem_acc`, `export virtio_check_mem_acc_cb`.
- Atlas domain: Driver Families / drivers/virtio.
- 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.