1 menu "Memory management options"
7 bool "Support for memory management hardware"
11 Some SH processors (such as SH-2/SH-2A) lack an MMU. In order to
12 boot on these systems, this option must not be set.
14 On other systems (such as the SH-3 and 4) where an MMU exists,
15 turning this off will boot the kernel on these machines with the
16 MMU implicitly switched off.
20 default "0x80000000" if MMU && SUPERH32
21 default "0x20000000" if MMU && SUPERH64
25 hex "Physical memory start address"
28 Computers built with Hitachi SuperH processors always
29 map the ROM starting at address zero. But the processor
30 does not specify the range that RAM takes.
32 The physical memory (RAM) start address will be automatically
33 set to 08000000. Other platforms, such as the Solution Engine
34 boards typically map RAM at 0C000000.
36 Tweak this only when porting to a new machine which does not
37 already have a defconfig. Changing it from the known correct
38 value on any of the known systems will only lead to disaster.
41 hex "Physical memory size"
44 This sets the default memory size assumed by your SH kernel. It can
45 be overridden as normal by the 'mem=' argument on the kernel command
46 line. If unsure, consult your board specifications or just leave it
47 as 0x04000000 which was the default value before this became
50 # Physical addressing modes
61 bool "Support 32-bit physical addressing through PMB"
62 depends on MMU && (CPU_SUBTYPE_SH7780 || CPU_SUBTYPE_SH7785)
66 If you say Y here, physical addressing will be extended to
67 32-bits through the SH-4A PMB. If this is not set, legacy
68 29-bit physical addressing will be used.
71 bool "Enable extended TLB mode"
72 depends on (CPU_SHX2 || CPU_SHX3) && MMU && EXPERIMENTAL
74 Selecting this option will enable the extended mode of the SH-X2
75 TLB. For legacy SH-X behaviour and interoperability, say N. For
76 all of the fun new features and a willingless to submit bug reports,
80 bool "Support vsyscall page"
81 depends on MMU && (CPU_SH3 || CPU_SH4)
84 This will enable support for the kernel mapping a vDSO page
85 in process space, and subsequently handing down the entry point
86 to the libc through the ELF auxiliary vector.
88 From the kernel side this is used for the signal trampoline.
89 For systems with an MMU that can afford to give up a page,
90 (the default value) say Y.
93 bool "Non Uniform Memory Access (NUMA) Support"
94 depends on MMU && SYS_SUPPORTS_NUMA && EXPERIMENTAL
97 Some SH systems have many various memories scattered around
98 the address space, each with varying latencies. This enables
99 support for these blocks by binding them to nodes and allowing
100 memory policies to be used for prioritizing and controlling
101 allocation behaviour.
105 default "3" if CPU_SUBTYPE_SHX3
107 depends on NEED_MULTIPLE_NODES
109 config ARCH_FLATMEM_ENABLE
113 config ARCH_SPARSEMEM_ENABLE
115 select SPARSEMEM_STATIC
117 config ARCH_SPARSEMEM_DEFAULT
120 config MAX_ACTIVE_REGIONS
122 default "6" if (CPU_SUBTYPE_SHX3 && SPARSEMEM)
123 default "2" if SPARSEMEM && (CPU_SUBTYPE_SH7722 || \
127 config ARCH_POPULATES_NODE_MAP
130 config ARCH_SELECT_MEMORY_MODEL
133 config ARCH_ENABLE_MEMORY_HOTPLUG
137 config ARCH_MEMORY_PROBE
139 depends on MEMORY_HOTPLUG
142 prompt "Kernel page size"
143 default PAGE_SIZE_8KB if X2TLB
144 default PAGE_SIZE_4KB
150 This is the default page size used by all SuperH CPUs.
156 This enables 8kB pages as supported by SH-X2 and later MMUs.
158 config PAGE_SIZE_64KB
160 depends on CPU_SH4 || CPU_SH5
162 This enables support for 64kB pages, possible on all SH-4
168 prompt "HugeTLB page size"
169 depends on HUGETLB_PAGE && (CPU_SH4 || CPU_SH5) && MMU
170 default HUGETLB_PAGE_SIZE_64K
172 config HUGETLB_PAGE_SIZE_64K
175 config HUGETLB_PAGE_SIZE_256K
179 config HUGETLB_PAGE_SIZE_1MB
182 config HUGETLB_PAGE_SIZE_4MB
186 config HUGETLB_PAGE_SIZE_64MB
190 config HUGETLB_PAGE_SIZE_512MB
200 menu "Cache configuration"
202 config SH7705_CACHE_32KB
203 bool "Enable 32KB cache size for SH7705"
204 depends on CPU_SUBTYPE_SH7705
207 config SH_DIRECT_MAPPED
208 bool "Use direct-mapped caching"
211 Selecting this option will configure the caches to be direct-mapped,
212 even if the cache supports a 2 or 4-way mode. This is useful primarily
213 for debugging on platforms with 2 and 4-way caches (SH7750R/SH7751R,
214 SH4-202, SH4-501, etc.)
216 Turn this option off for platforms that do not have a direct-mapped
217 cache, and you have no need to run the caches in such a configuration.
221 default CACHE_WRITEBACK if CPU_SH2A || CPU_SH3 || CPU_SH4 || CPU_SH5
222 default CACHE_WRITETHROUGH if (CPU_SH2 && !CPU_SH2A)
224 config CACHE_WRITEBACK
226 depends on CPU_SH2A || CPU_SH3 || CPU_SH4 || CPU_SH5
228 config CACHE_WRITETHROUGH
231 Selecting this option will configure the caches in write-through
232 mode, as opposed to the default write-back configuration.
234 Since there's sill some aliasing issues on SH-4, this option will
235 unfortunately still require the majority of flushing functions to
236 be implemented to deal with aliasing.