Lines Matching refs:memory
10 Hidden option to enable virtual memory Kconfigs.
60 memory that is mapped at boot.
63 physical memory have dissimilar alignment.
70 how much total memory can be used for page tables.
73 size of the virtual region for runtime memory mappings. This is needed
75 such as VSDO pages, memory mapped thread stacks, and anonymous memory
78 Systems with very large amounts of memory (such as 512M or more)
80 implement a notion of "high" memory in Zephyr to work around physical
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
94 memory space will fail.
108 This option is enabled when the CPU's memory management unit is active
116 Size of memory pages. Varies per MMU but 4K is common. For MMUs that
129 bool "Allow on-demand memory mappings"
133 When this is enabled, RAM-based memory mappings don't actually
134 allocate memory at mem_map time. They are made to be populated
158 paging that do not count towards free memory. This is to
161 all page frames via anonymous memory mappings.
216 Use custom memory range check functions instead of the generic