kernel/time/clocksource-wdtest.c

File Facts

System

Linux kernel

Corpus path

kernel/time/clocksource-wdtest.c

Extension

.c

Size

5051 bytes

Lines

199

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

Inferred role

Core OS: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• 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/clocksource.h
• linux/delay.h
• linux/module.h
• linux/kthread.h
• tick-internal.h
• timekeeping_internal.h

Detected Declarations

• enum wdtest_states
• function wdtest_get_offset
• function wdtest_ktime_read
• function wdtest_clocksource_reset
• function wdtest_execute
• function wdtest_run
• function wdtest_func
• function clocksource_wdtest_init
• function clocksource_wdtest_cleanup
• module init clocksource_wdtest_init

Annotated Snippet

module_init(clocksource_wdtest_init);

static void clocksource_wdtest_cleanup(void)
{
	if (wdtest_thread)
		kthread_stop(wdtest_thread);
}
module_exit(clocksource_wdtest_cleanup);

Annotation

• Immediate include surface: `linux/clocksource.h`, `linux/delay.h`, `linux/module.h`, `linux/kthread.h`, `tick-internal.h`, `timekeeping_internal.h`.
• Detected declarations: `enum wdtest_states`, `function wdtest_get_offset`, `function wdtest_ktime_read`, `function wdtest_clocksource_reset`, `function wdtest_execute`, `function wdtest_run`, `function wdtest_func`, `function clocksource_wdtest_init`, `function clocksource_wdtest_cleanup`, `module init clocksource_wdtest_init`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• 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.