Lines Matching +full:ram +full:- +full:region

3 # SPDX-License-Identifier: Apache-2.0
23 	  address from DTS, in which case RAM will be identity-mapped. Some
24 	  architectures may require RAM to be mapped in this way; they may have
25 	  just one RAM region and doing this makes linking much simpler, as
26 	  at least when the kernel boots all virtual RAM addresses are the same
28 	  this for non-pinned page frames).
30 	  Otherwise, if RAM isn't identity-mapped:
35 	  the kernel's address space, such as not overlapping physical RAM
36 	  regions if RAM is not identity-mapped, or the virtual and physical
38 	  double-linking of paging structures to make the instruction pointer
42 	  page tables are in use, they all have the same virtual-to-physical
50 	  if this is not the same offset from the beginning of RAM.
53 	  build-time cases, or when a physical address cannot be looked up
56 	      virt = phys + ((KERNEL_VM_BASE + KERNEL_VM_OFFSET) -
73 	  size of the virtual region for runtime memory mappings. This is needed
74 	  for mapping driver MMIO regions, as well as special RAM mapping use-cases
79 	  will want to use a 64-bit build of Zephyr, there are no plans to
81 	  RAM size larger than the defined bounds of the virtual address space.
84 	bool "Memory region direct-map support"
87 	  This enables the direct-map support, namely the region can be 1:1
90 	  If the specific memory region is in the virtual memory space and
92 	  region from the virtual memory space and do the mapping, otherwise
127 	bool "Allow on-demand memory mappings"
131 	  When this is enabled, RAM-based memory mappings don't actually
136 	bool "Allow interrupts during page-ins/outs"