arch/riscv/include/asm/cacheflush.h

File Facts

System

Linux kernel

Corpus path

arch/riscv/include/asm/cacheflush.h

Extension

.h

Size

2878 bytes

Lines

109

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.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/mm.h
• asm-generic/cacheflush.h

Detected Declarations

• function Copyright
• function local_flush_icache_range
• function flush_dcache_folio
• function flush_dcache_page
• function mark_new_valid_map
• function flush_cache_vmap
• function flush_icache_range
• function riscv_noncoherent_supported

Annotated Snippet

static inline void riscv_noncoherent_supported(void) {}
static inline void riscv_set_dma_cache_alignment(void) {}
#endif

/*
 * Bits in sys_riscv_flush_icache()'s flags argument.
 */
#define SYS_RISCV_FLUSH_ICACHE_LOCAL 1UL
#define SYS_RISCV_FLUSH_ICACHE_ALL   (SYS_RISCV_FLUSH_ICACHE_LOCAL)

#include <asm-generic/cacheflush.h>

#endif /* _ASM_RISCV_CACHEFLUSH_H */

Annotation

• Immediate include surface: `linux/mm.h`, `asm-generic/cacheflush.h`.
• Detected declarations: `function Copyright`, `function local_flush_icache_range`, `function flush_dcache_folio`, `function flush_dcache_page`, `function mark_new_valid_map`, `function flush_cache_vmap`, `function flush_icache_range`, `function riscv_noncoherent_supported`.
• 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.