arch/s390/kernel/vdso/vdso_generic.c
Source file repositories/reference/linux-study-clean/arch/s390/kernel/vdso/vdso_generic.c
File Facts
- System
- Linux kernel
- Corpus path
arch/s390/kernel/vdso/vdso_generic.c- Extension
.c- Size
- 481 bytes
- Lines
- 20
- Domain
- Architecture Layer
- Bucket
- arch/s390
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
../../../../lib/vdso/gettimeofday.cvdso.h
Detected Declarations
function __s390_vdso_gettimeofdayfunction __s390_vdso_clock_gettimefunction __s390_vdso_clock_getres
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include "../../../../lib/vdso/gettimeofday.c"
#include "vdso.h"
int __s390_vdso_gettimeofday(struct __kernel_old_timeval *tv,
struct timezone *tz)
{
return __cvdso_gettimeofday(tv, tz);
}
int __s390_vdso_clock_gettime(clockid_t clock, struct __kernel_timespec *ts)
{
return __cvdso_clock_gettime(clock, ts);
}
int __s390_vdso_clock_getres(clockid_t clock, struct __kernel_timespec *ts)
{
return __cvdso_clock_getres(clock, ts);
}
Annotation
- Immediate include surface: `../../../../lib/vdso/gettimeofday.c`, `vdso.h`.
- Detected declarations: `function __s390_vdso_gettimeofday`, `function __s390_vdso_clock_gettime`, `function __s390_vdso_clock_getres`.
- Atlas domain: Architecture Layer / arch/s390.
- 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.