Searched full:paging (Results 1 – 25 of 56) sorted by relevance
123
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 27 as their physical address (demand paging at runtime may later modify
38 double-linking of paging structures to make the instruction pointer
120 bool "Demand paging [EXPERIMENTAL]"
123 Enable demand paging. Requires architecture support in how the kernel
135 at access time using the demand paging mechanism instead.
153 int "Number of page frames reserved for paging"
158 paging that do not count towards free memory. This is to
159 ensure that there are some page frames available for paging
164 bool "Gather Demand Paging Statistics"
166 This enables gathering various statistics related to demand paging,
[all …]
|
| D | kheap.c | 29 * paging mechanism to be initialized before we can initialize in statics_init()
60 /* Need to wait for paging mechanism to be initialized before
|
| /Zephyr-latest/samples/subsys/demand_paging/ |
| D | README.rst | 1 .. zephyr:code-sample:: demand-paging
2 :name: Demand paging
3 :relevant-api: mem-demand-paging
5 Leverage demand paging to deal with code bigger than available RAM.
10 This sample demonstrates how demand paging can be leveraged to deal with
49 To actually view the underlying demand paging subsystem at work, debug
|
| D | sample.yaml | 2 description: On-Demand paging of firmware larger than available memory
3 name: demand-paging
|
| /Zephyr-latest/subsys/demand_paging/backing_store/ |
| D | Kconfig | 20 demonstration and testing of the demand paging feature.
27 for demand paging. The qemu_x86_tiny.ld linker script puts
29 area, allowing testing of the demand paging mechanism on
36 This is used to do on-demand paging of code and data marked with
49 cases for demand paging assume that there are at least 16 pages of
|
| D | backing_store_qemu_x86_tiny.c | 12 * for demand paging. The qemu_x86_tiny.ld linker script puts
14 * area, allowing testing of the demand paging mechanism on
|
| D | ram.c | 17 * demand paging feature. In production there are basically two types of
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | demand_paging.rst | 3 Demand Paging
6 Demand paging provides a mechanism where data is only brought into physical
14 in any page frames, a page fault occurs. The paging code then brings in
22 paged out and the corresponding page frame is now free. The paging code
28 There are functions where paging in and out can be invoked manually
36 page in can be executed faster as the paging code does not need to invoke
87 Paging Statistics
90 Paging statistics can be obtained via various function calls when
122 called from the kernel paging code:
138 as set, the paging code signals to the backing store to write
[all …]
|
| D | virtual_memory.rst | 15 between physical and virtual memory address spaces, if demand paging
27 Note that demand paging needs to be explicitly enabled.
30 memory space, without enabling demand paging, all virtually
130 some addresses are reserved to support demand paging.
|
| /Zephyr-latest/include/zephyr/kernel/mm/ |
| D | demand_paging.h | 16 * @defgroup demand_paging Demand Paging
21 * @defgroup mem-demand-paging Demand Paging APIs
35 * Paging Statistics.
66 * Paging Statistics Histograms.
125 * Pin an aligned virtual data region, paging in as necessary
152 * Get the paging statistics since system startup
154 * This populates the paging statistics struct being passed in
157 * @param[in,out] stats Paging statistics struct to be filled.
163 * Get the paging statistics since system startup for a thread
165 * This populates the paging statistics struct being passed in
[all …]
|
| /Zephyr-latest/subsys/demand_paging/ |
| D | Kconfig | 4 menu "Demand Paging modules"
|
| /Zephyr-latest/include/zephyr/kernel/internal/ |
| D | mm.h | 34 * Note that when demand paging is active, these will only work with page
133 * the above checks won't be sufficient with demand paging in k_mem_phys_addr()
170 * the above check won't be sufficient with demand paging in k_mem_virt_addr()
210 * frames. It may conflict with anonymous memory mappings and demand paging
244 * It may conflict with anonymous memory mappings and demand paging and
302 * or insufficient memory for paging structures.
|
| /Zephyr-latest/include/zephyr/kernel/ |
| D | mm.h | 123 * be allocated initially. Allocation will happen through demand paging when
142 * If demand paging is enabled, it may still be possible to allocate more.
188 * or insufficient memory for paging structures.
201 * be allocated initially. Allocation will happen through demand paging when
233 * space to establish the mapping, or insufficient memory for paging
|
| /Zephyr-latest/arch/x86/include/ia32/ |
| D | kernel_arch_func.h | 42 /* ASM code to fiddle with registers to enable the MMU with PAE paging */
|
| /Zephyr-latest/arch/x86/include/ |
| D | x86_mmu.h | 54 * These bits ignored for all paging modes.
86 * @param paging_level [out] what paging level the entry was found at.
153 /* Set CR3 to a physical address. There must be a valid top-level paging
235 /* Early-boot paging setup tasks, called from prep_c */
|
| D | kernel_arch_data.h | 53 #define CR0_PG BIT(31) /* enable paging */
|
| /Zephyr-latest/arch/x86/ |
| D | gen_mmu.py | 9 For additional detail on paging and x86 memory management, please
38 - The mapping is always double-mapped at the top-level paging structure
40 with respect to the scope of top-level paging structure entries.
41 This allows the same second-level paging structure(s) to be used for
65 top-level paging structure as it is written out last.
179 # Hard-coded flags for intermediate paging levels. Permissive, we only control
226 """Number of entries in the table. Varies by table type and paging
336 """Represents a complete set of page tables for any paging mode"""
362 """Class hierarchy of paging levels, with the first entry being
435 debug("Reserving paging structures for 0x%x (0x%x)" %
[all …]
|
| /Zephyr-latest/include/zephyr/arch/x86/ |
| D | pagetables.ld | 22 /* Top-level paging structure is the last thing in this section */
|
| /Zephyr-latest/kernel/include/ |
| D | mmu.h | 116 * and we generate paging structures based on CONFIG_SRAM_BASE_ADDRESS
120 * properties and shouldn't be used generically for demand paging or
337 * @brief Location of the scratch page used for demand paging.
348 * Core kernel demand paging APIs
355 * paging mechanism and were not errors.
|
| /Zephyr-latest/subsys/demand_paging/eviction/ |
| D | Kconfig | 4 # Demand paging sample eviction algorithms
|
| D | nru.c | 6 * Not Recently Used (NRU) eviction algorithm for demand paging
|
| /Zephyr-latest/arch/x86/core/ia32/ |
| D | crt0.S | 55 /* Enable paging. If virtual memory is enabled, the instruction pointer
58 * CONFIG_KERNEL_VM_BASE using the same paging structures.
87 /* Enable paging (CR0.PG, bit 31) / write protect (CR0.WP, bit 16) */
276 * paging mechanism has been initialized.
|
| /Zephyr-latest/tests/kernel/mem_protect/demand_paging/mem_map/src/ |
| D | main.c | 54 #error "Need to define paging histogram bounds"
372 /* Test if we can get paging statistics under usermode */
430 /* Test if we can get paging timing histograms */
|
| /Zephyr-latest/arch/x86/core/ |
| D | x86_mmu.c | 58 * paging structures.
73 * Definitions for building an ontology of paging levels and capabilities
77 /* Data structure describing the characteristics of a particular paging
84 /* Number of entries in this paging structure */
99 /* Flags for all entries in intermediate paging levels.
101 * three paging modes.
114 /* Paging level ontology for the selected paging mode.
1177 /* There's a gap in the "64-bit" address space, as 4-level paging in range_map()
1675 * paging levels.
1680 * paging level.
[all …]
|
| /Zephyr-latest/include/zephyr/xen/public/ |
| D | domctl.h | 38 /* Use hardware-assisted paging if available? */
126 /* domain has hardware assisted paging */
405 * Get or set the paging memory pool size. The size is in bytes.
|
123
