tools/testing/selftests/timers/nanosleep.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/timers/nanosleep.c

Extension

.c

Size

4967 bytes

Lines

214

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• errno.h
• stdio.h
• stdlib.h
• time.h
• sys/time.h
• sys/timex.h
• string.h
• signal.h
• include/vdso/time64.h
• kselftest.h

Detected Declarations

• function in_order
• function timespec_add
• function nanosleep_test
• function dummy_event_handler
• function main

Annotated Snippet

while (length <= (NSEC_PER_SEC * 10)) {
			ret = nanosleep_test(clockid, length);
			if (ret == UNSUPPORTED) {
				ksft_test_result_skip("%-31s\n", clockstring(clockid));
				goto next;
			}
			if (ret < 0) {
				ksft_test_result_fail("%-31s\n", clockstring(clockid));
				ksft_exit_fail();
			}
			length *= 100;
		}
		ret = nanosleep_test_remaining(clockid);
		if (ret < 0) {
			ksft_test_result_fail("%-31s\n", clockstring(clockid));
			ksft_exit_fail();
		}
		ksft_test_result_pass("%-31s\n", clockstring(clockid));
next:
		ret = 0;
	}
	ksft_exit_pass();
}

Annotation

• Immediate include surface: `errno.h`, `stdio.h`, `stdlib.h`, `time.h`, `sys/time.h`, `sys/timex.h`, `string.h`, `signal.h`.
• Detected declarations: `function in_order`, `function timespec_add`, `function nanosleep_test`, `function dummy_event_handler`, `function main`.
• Atlas domain: Support Tooling And Documentation / tools.
• 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.