arch/riscv/include/asm/sync_core.h

File Facts

System

Linux kernel

Corpus path

arch/riscv/include/asm/sync_core.h

Extension

.h

Size

689 bytes

Lines

30

Domain

Architecture Layer

Bucket

arch/riscv

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

• No C-style include directives detected by the generator.

Detected Declarations

• function sync_core_before_usermode
• function switch_mm
• function prepare_sync_core_cmd

Annotated Snippet

#ifndef _ASM_RISCV_SYNC_CORE_H
#define _ASM_RISCV_SYNC_CORE_H

/*
 * RISC-V implements return to user-space through an xRET instruction,
 * which is not core serializing.
 */
static inline void sync_core_before_usermode(void)
{
	asm volatile ("fence.i" ::: "memory");
}

#ifdef CONFIG_SMP
/*
 * Ensure the next switch_mm() on every CPU issues a core serializing
 * instruction for the given @mm.
 */
static inline void prepare_sync_core_cmd(struct mm_struct *mm)
{
	cpumask_setall(&mm->context.icache_stale_mask);
}
#else
static inline void prepare_sync_core_cmd(struct mm_struct *mm)
{
}
#endif /* CONFIG_SMP */

#endif /* _ASM_RISCV_SYNC_CORE_H */

Annotation

• Detected declarations: `function sync_core_before_usermode`, `function switch_mm`, `function prepare_sync_core_cmd`.
• Atlas domain: Architecture Layer / arch/riscv.
• 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.