arch/loongarch/include/asm/timex.h
Source file repositories/reference/linux-study-clean/arch/loongarch/include/asm/timex.h
File Facts
- System
- Linux kernel
- Corpus path
arch/loongarch/include/asm/timex.h- Extension
.h- Size
- 837 bytes
- Lines
- 58
- Domain
- Architecture Layer
- Bucket
- arch/loongarch
- 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.
Dependency Surface
linux/compiler.hasm/cpu.hasm/cpu-features.h
Detected Declarations
function get_cyclesfunction get_cycles_hifunction get_cycles64
Annotated Snippet
#ifndef _ASM_TIMEX_H
#define _ASM_TIMEX_H
#ifdef __KERNEL__
#include <linux/compiler.h>
#include <asm/cpu.h>
#include <asm/cpu-features.h>
typedef unsigned long cycles_t;
#define get_cycles get_cycles
static inline cycles_t get_cycles(void)
{
#ifdef CONFIG_32BIT
return rdtime_l();
#else
return rdtime_d();
#endif
}
#ifdef CONFIG_32BIT
#define get_cycles_hi get_cycles_hi
static inline cycles_t get_cycles_hi(void)
{
return rdtime_h();
}
#endif
static inline u64 get_cycles64(void)
{
#ifdef CONFIG_32BIT
u32 hi, lo;
do {
hi = rdtime_h();
lo = rdtime_l();
} while (hi != rdtime_h());
return ((u64)hi << 32) | lo;
#else
return rdtime_d();
#endif
}
#endif /* __KERNEL__ */
#endif /* _ASM_TIMEX_H */
Annotation
- Immediate include surface: `linux/compiler.h`, `asm/cpu.h`, `asm/cpu-features.h`.
- Detected declarations: `function get_cycles`, `function get_cycles_hi`, `function get_cycles64`.
- Atlas domain: Architecture Layer / arch/loongarch.
- 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.