lib/test_debug_virtual.c

File Facts

System

Linux kernel

Corpus path

lib/test_debug_virtual.c

Extension

.c

Size

965 bytes

Lines

52

Domain

Kernel Services

Bucket

lib

Inferred role

Kernel Services: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.

• Shared kernel service surface used by multiple subsystems, including helpers, cryptography, virtualization support, and async I/O infrastructure.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• 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.h
• linux/module.h
• linux/export.h
• linux/mm.h
• linux/vmalloc.h
• linux/slab.h
• linux/sizes.h
• linux/io.h
• asm/page.h
• asm/bootinfo.h

Detected Declarations

• struct foo
• function test_debug_virtual_init
• function test_debug_virtual_exit
• module init test_debug_virtual_init

Annotated Snippet

module_init(test_debug_virtual_init);

static void __exit test_debug_virtual_exit(void)
{
	kfree(foo);
}
module_exit(test_debug_virtual_exit);

MODULE_LICENSE("GPL");
MODULE_DESCRIPTION("Test module for CONFIG_DEBUG_VIRTUAL");

Annotation

• Immediate include surface: `linux/kernel.h`, `linux/module.h`, `linux/export.h`, `linux/mm.h`, `linux/vmalloc.h`, `linux/slab.h`, `linux/sizes.h`, `linux/io.h`.
• Detected declarations: `struct foo`, `function test_debug_virtual_init`, `function test_debug_virtual_exit`, `module init test_debug_virtual_init`.
• Atlas domain: Kernel Services / lib.
• 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.