drivers/md/dm-vdo/time-utils.h

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-vdo/time-utils.h

Extension

.h

Size

562 bytes

Lines

29

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.

Dependency Surface

• linux/ktime.h
• linux/time.h
• linux/types.h

Detected Declarations

• function ktime_to_seconds
• function current_time_ns
• function current_time_us

Annotated Snippet

#ifndef UDS_TIME_UTILS_H
#define UDS_TIME_UTILS_H

#include <linux/ktime.h>
#include <linux/time.h>
#include <linux/types.h>

static inline s64 ktime_to_seconds(ktime_t reltime)
{
	return reltime / NSEC_PER_SEC;
}

static inline ktime_t current_time_ns(clockid_t clock)
{
	return clock == CLOCK_MONOTONIC ? ktime_get_ns() : ktime_get_real_ns();
}

static inline ktime_t current_time_us(void)
{
	return current_time_ns(CLOCK_REALTIME) / NSEC_PER_USEC;
}

#endif /* UDS_TIME_UTILS_H */

Annotation

• Immediate include surface: `linux/ktime.h`, `linux/time.h`, `linux/types.h`.
• Detected declarations: `function ktime_to_seconds`, `function current_time_ns`, `function current_time_us`.
• 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.