1menu "Memory management"
2
3config RT_PAGE_AFFINITY_BLOCK_SIZE
4    hex "Affinity block size in bytes for page management"
5    default 0x1000
6    help
7        Page affinity block can be used to resolve the VIPT aliasing problem.
8        It should be set to `1ul << ((index + block) - page_offset)` in this case.
9        You could also exploit this as a tunning for cache coloring.
10
11config RT_PAGE_MAX_ORDER
12    int "Max order of pages allocatable by page allocator"
13    default 11
14    depends on ARCH_MM_MMU
15    help
16        For example, A value of 11 means the maximum chunk of contiguous memory
17        allocatable by page system is 2^(11 + ARCH_PAGE_BITS - 1) Bytes.
18        Large memory requirement can consume all system resource, and should
19        consider reserved memory instead to enhance system endurance.
20        Max order should at least satisfied usage by huge page.
21
22config RT_USING_MEMBLOCK
23    bool "Using memblock"
24    default n
25    help
26        Using memblock to record memory infomation in init time
27
28config RT_INIT_MEMORY_REGIONS
29    int "The max number of memory block regions in init time"
30    depends on RT_USING_MEMBLOCK
31    range 1 1024
32    default 128
33    help
34        During the system initialization phase, the kernel divides
35        memory into different types of regions. This variable specifies
36        the maximum number of regions supported by the system.
37
38menu "Debugging"
39    config RT_DEBUGGING_ALIASING
40        bool "Using aliasing paging debugger"
41        default n
42
43    config RT_DEBUGING_PAGE_LEAK
44        bool "Using page leaking tracer"
45        default n
46
47    config RT_DEBUGGING_PAGE_POISON
48        bool "Using page poisoner to detect illegal usage"
49        default n
50endmenu
51
52endmenu
53