drivers/md/dm-vdo/thread-device.h

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-vdo/thread-device.h

Extension

.h

Size

435 bytes

Lines

21

Domain

Driver Families

Bucket

drivers/md

Inferred role

Driver Families: implementation source

Status

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

Dependency Surface

• thread-registry.h

Detected Declarations

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

Annotated Snippet

#ifndef VDO_THREAD_DEVICE_H
#define VDO_THREAD_DEVICE_H

#include "thread-registry.h"

void vdo_register_thread_device_id(struct registered_thread *new_thread,
				   unsigned int *id_ptr);

void vdo_unregister_thread_device_id(void);

int vdo_get_thread_device_id(void);

void vdo_initialize_thread_device_registry(void);

#endif /* VDO_THREAD_DEVICE_H */

Annotation

• Immediate include surface: `thread-registry.h`.
• Atlas domain: Driver Families / drivers/md.
• Implementation status: source 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.