include/vdso/helpers.h
Source file repositories/reference/linux-study-clean/include/vdso/helpers.h
File Facts
- System
- Linux kernel
- Corpus path
include/vdso/helpers.h- Extension
.h- Size
- 3064 bytes
- Lines
- 117
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
asm/barrier.hvdso/datapage.hvdso/processor.hvdso/clocksource.h
Detected Declarations
function vdso_is_timens_clockfunction vdso_read_beginfunction vdso_read_beginfunction vdso_read_retryfunction vdso_write_seq_beginfunction vdso_write_seq_endfunction vdso_write_begin_clockfunction vdso_write_end_clockfunction vdso_write_beginfunction vdso_write_end
Annotated Snippet
#ifndef __VDSO_HELPERS_H
#define __VDSO_HELPERS_H
#ifndef __ASSEMBLY__
#include <asm/barrier.h>
#include <vdso/datapage.h>
#include <vdso/processor.h>
#include <vdso/clocksource.h>
static __always_inline bool vdso_is_timens_clock(const struct vdso_clock *vc)
{
return IS_ENABLED(CONFIG_TIME_NS) && vc->clock_mode == VDSO_CLOCKMODE_TIMENS;
}
static __always_inline u32 vdso_read_begin(const struct vdso_clock *vc)
{
u32 seq;
while (unlikely((seq = READ_ONCE(vc->seq)) & 1))
cpu_relax();
smp_rmb();
return seq;
}
/*
* Variant of vdso_read_begin() to handle VDSO_CLOCKMODE_TIMENS.
*
* Time namespace enabled tasks have a special VVAR page installed which has
* vc->seq set to 1 and vc->clock_mode set to VDSO_CLOCKMODE_TIMENS. For non
* time namespace affected tasks this does not affect performance because if
* vc->seq is odd, i.e. a concurrent update is in progress the extra check for
* vc->clock_mode is just a few extra instructions while spin waiting for
* vc->seq to become even again.
*/
static __always_inline bool vdso_read_begin_timens(const struct vdso_clock *vc, u32 *seq)
{
while (unlikely((*seq = READ_ONCE(vc->seq)) & 1)) {
if (vdso_is_timens_clock(vc))
return true;
cpu_relax();
}
smp_rmb();
return false;
}
static __always_inline u32 vdso_read_retry(const struct vdso_clock *vc,
u32 start)
{
u32 seq;
smp_rmb();
seq = READ_ONCE(vc->seq);
return unlikely(seq != start);
}
static __always_inline void vdso_write_seq_begin(struct vdso_clock *vc)
{
/*
* WRITE_ONCE() is required otherwise the compiler can validly tear
* updates to vc->seq and it is possible that the value seen by the
* reader is inconsistent.
*/
WRITE_ONCE(vc->seq, vc->seq + 1);
}
static __always_inline void vdso_write_seq_end(struct vdso_clock *vc)
{
/*
* WRITE_ONCE() is required otherwise the compiler can validly tear
* updates to vc->seq and it is possible that the value seen by the
* reader is inconsistent.
*/
WRITE_ONCE(vc->seq, vc->seq + 1);
}
static __always_inline void vdso_write_begin_clock(struct vdso_clock *vc)
{
vdso_write_seq_begin(vc);
/* Ensure the sequence invalidation is visible before data is modified */
smp_wmb();
}
static __always_inline void vdso_write_end_clock(struct vdso_clock *vc)
{
/* Ensure the data update is visible before the sequence is set valid again */
smp_wmb();
vdso_write_seq_end(vc);
Annotation
- Immediate include surface: `asm/barrier.h`, `vdso/datapage.h`, `vdso/processor.h`, `vdso/clocksource.h`.
- Detected declarations: `function vdso_is_timens_clock`, `function vdso_read_begin`, `function vdso_read_begin`, `function vdso_read_retry`, `function vdso_write_seq_begin`, `function vdso_write_seq_end`, `function vdso_write_begin_clock`, `function vdso_write_end_clock`, `function vdso_write_begin`, `function vdso_write_end`.
- Atlas domain: Repository Root And Misc / include.
- 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.