arch/s390/include/asm/kfence.h
Source file repositories/reference/linux-study-clean/arch/s390/include/asm/kfence.h
File Facts
- System
- Linux kernel
- Corpus path
arch/s390/include/asm/kfence.h- Extension
.h- Size
- 734 bytes
- Lines
- 32
- Domain
- Architecture Layer
- Bucket
- arch/s390
- 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
linux/mm.hlinux/kfence.hasm/set_memory.hasm/page.h
Detected Declarations
function arch_kfence_init_poolfunction kfence_protect_page
Annotated Snippet
#ifndef _ASM_S390_KFENCE_H
#define _ASM_S390_KFENCE_H
#include <linux/mm.h>
#include <linux/kfence.h>
#include <asm/set_memory.h>
#include <asm/page.h>
void __kernel_map_pages(struct page *page, int numpages, int enable);
static __always_inline bool arch_kfence_init_pool(void)
{
#ifdef CONFIG_KFENCE
unsigned long pool_pages = KFENCE_POOL_SIZE >> PAGE_SHIFT;
set_memory_4k((unsigned long)__kfence_pool, pool_pages);
#endif
return true;
}
#define arch_kfence_test_address(addr) ((addr) & PAGE_MASK)
static inline bool kfence_protect_page(unsigned long addr, bool protect)
{
__kernel_map_pages(virt_to_page((void *)addr), 1, !protect);
return true;
}
#endif /* _ASM_S390_KFENCE_H */
Annotation
- Immediate include surface: `linux/mm.h`, `linux/kfence.h`, `asm/set_memory.h`, `asm/page.h`.
- Detected declarations: `function arch_kfence_init_pool`, `function kfence_protect_page`.
- Atlas domain: Architecture Layer / arch/s390.
- 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.