Searched refs:fixmap (Results 1 – 11 of 11) sorted by relevance
20 static __always_inline void *patch_map(void *addr, int fixmap) in patch_map() argument33 return (void *)set_fixmap_offset(fixmap, phys); in patch_map()36 static void patch_unmap(int fixmap) in patch_unmap() argument38 clear_fixmap(fixmap); in patch_unmap()
31 static void __kprobes *patch_map(void *addr, int fixmap) in patch_map() argument43 return (void *)set_fixmap_offset(fixmap, phys); in patch_map()46 static void __kprobes patch_unmap(int fixmap) in patch_unmap() argument48 clear_fixmap(fixmap); in patch_unmap()
126 分配内存，但不能直接访问它（因为直接映射还不存在），所以它使用fixmap135 通过fixmap进行设备树映射140 fixmap区域来映射设备树。这确保设备树可以通过两种虚拟映射访问。
55 ffffffc6fee00000 | -228 GB | ffffffc6feffffff | 2 MB | fixmap91 ffff8d7ffee00000 | -114.5 TB | ffff8d7ffeffffff | 2 MB | fixmap
50 ffffffc4fea00000 | -236 GB | ffffffc4feffffff | 6 MB | fixmap87 ffff8d7ffea00000 | -114.5 TB | ffff8d7ffeffffff | 6 MB | fixmap123 ff1bfffffea00000 | -57 PB | ff1bfffffeffffff | 6 MB | fixmap
132 it uses temporary mappings in the fixmap region to be able to access the142 Devicetree mapping via fixmap147 ``setup_vm_final()``, the RISC-V kernel uses the fixmap region to map the
6 obj-y := init.o fault.o ioremap.o fixmap.o
81 …FIXADDR_START | ~-11 MB | ffffffffff5fffff | ~0.5 MB | kernel-internal fixmap range, variable s…151 …FIXADDR_START | ~-11 MB | ffffffffff5fffff | ~0.5 MB | kernel-internal fixmap range, variable s…
9 fixmap area and occupies one eighth of the total kernel virtual memory space.
48 cpu_entry_area' structure which is placed in the fixmap which gives
1057 debugging is enabled, which uses half of the per-CPU fixmap