include/linux/ioremap.h
Source file repositories/reference/linux-study-clean/include/linux/ioremap.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/ioremap.h- Extension
.h- Size
- 744 bytes
- Lines
- 32
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
Dependency Surface
linux/kasan.hasm/pgtable.hasm/vmalloc.h
Detected Declarations
function is_ioremap_addrfunction is_ioremap_addr
Annotated Snippet
#ifndef _LINUX_IOREMAP_H
#define _LINUX_IOREMAP_H
#include <linux/kasan.h>
#include <asm/pgtable.h>
#include <asm/vmalloc.h>
#if defined(CONFIG_HAS_IOMEM) || defined(CONFIG_GENERIC_IOREMAP)
/*
* Ioremap often, but not always uses the generic vmalloc area. E.g on
* Power ARCH, it could have different ioremap space.
*/
#ifndef IOREMAP_START
#define IOREMAP_START VMALLOC_START
#define IOREMAP_END VMALLOC_END
#endif
static inline bool is_ioremap_addr(const void *x)
{
unsigned long addr = (unsigned long)kasan_reset_tag(x);
return addr >= IOREMAP_START && addr < IOREMAP_END;
}
#else
static inline bool is_ioremap_addr(const void *x)
{
return false;
}
#endif
#endif /* _LINUX_IOREMAP_H */
Annotation
- Immediate include surface: `linux/kasan.h`, `asm/pgtable.h`, `asm/vmalloc.h`.
- Detected declarations: `function is_ioremap_addr`, `function is_ioremap_addr`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.