Lines Matching full:virtual

3 Virtual Memory
6 Virtual memory (VM) in Zephyr provides developers with the ability to fine tune
7 access to memory. To utilize virtual memory, the platform must support
9 the target of Zephyr mainly being embedded systems, virtual memory
15   between physical and virtual memory address spaces, if demand paging
20   Basic virtual memory support does not utilize secondary storage to
25     secondary storage as a backing store for virtual memory, thus
29   * Although the virtual memory space can be larger than physical
41 virtual memory.
43 * :kconfig:option:`CONFIG_MMU`: must be enabled for virtual memory support in
48 * :kconfig:option:`CONFIG_KERNEL_VM_BASE`: base address of virtual address space.
50 * :kconfig:option:`CONFIG_KERNEL_VM_SIZE`: size of virtual address space.
60   virtual and physical addresses, instead of kernel choosing addresses within
61   the virtual address space. This is useful for mapping device MMIO regions for
68 This is an overview of the memory map of the virtual memory address space.
98    | Reserved     | <- special purpose virtual page(s) of size K_MEM_VM_RESERVED
101 * ``K_MEM_VIRT_RAM_START`` is the beginning of the virtual memory address space.
105 * ``K_MEM_VIRT_RAM_SIZE`` is the size of the virtual memory address space.
112   script. This is the virtual address of the beginning of the kernel image at
116   script. This is the virtual address of the end of the kernel image at boot time.
118 * ``K_MEM_VM_FREE_START`` is the beginning of the virtual address space where addresses
122   * If it is enabled, which means all physical memory are mapped in virtual
133 Virtual Memory Mappings
170 The unused physical memory can be mapped in virtual address space on demand.
178   * The address returned is inside the virtual address space between
183   * Guard pages immediately before and after the mapped virtual region are