arch/riscv/include/asm/kfence.h
Source file repositories/reference/linux-study-clean/arch/riscv/include/asm/kfence.h
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/include/asm/kfence.h- Extension
.h- Size
- 735 bytes
- Lines
- 36
- 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.
Dependency Surface
linux/kfence.hlinux/pfn.hasm-generic/pgalloc.hasm/cacheflush.hasm/pgtable.h
Detected Declarations
function arch_kfence_init_poolfunction kfence_protect_page
Annotated Snippet
#ifndef _ASM_RISCV_KFENCE_H
#define _ASM_RISCV_KFENCE_H
#include <linux/kfence.h>
#include <linux/pfn.h>
#include <asm-generic/pgalloc.h>
#include <asm/cacheflush.h>
#include <asm/pgtable.h>
static inline bool arch_kfence_init_pool(void)
{
return true;
}
static inline bool kfence_protect_page(unsigned long addr, bool protect)
{
pte_t *pte = virt_to_kpte(addr);
if (protect) {
set_pte(pte, __pte(pte_val(ptep_get(pte)) & ~_PAGE_PRESENT));
} else {
set_pte(pte, __pte(pte_val(ptep_get(pte)) | _PAGE_PRESENT));
mark_new_valid_map();
}
preempt_disable();
local_flush_tlb_kernel_range(addr, addr + PAGE_SIZE);
preempt_enable();
return true;
}
#endif /* _ASM_RISCV_KFENCE_H */
Annotation
- Immediate include surface: `linux/kfence.h`, `linux/pfn.h`, `asm-generic/pgalloc.h`, `asm/cacheflush.h`, `asm/pgtable.h`.
- Detected declarations: `function arch_kfence_init_pool`, `function kfence_protect_page`.
- 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.