Commit | Line | Data |
---|---|---|
867e359b | 1 | # For a description of the syntax of this configuration file, |
5fb682b0 | 2 | # see Documentation/kbuild/kconfig-language.txt. |
867e359b | 3 | |
8df27406 | 4 | config TILE |
867e359b | 5 | def_bool y |
8df27406 TG |
6 | select HAVE_KVM if !TILEGX |
7 | select GENERIC_FIND_FIRST_BIT | |
8df27406 TG |
8 | select USE_GENERIC_SMP_HELPERS |
9 | select CC_OPTIMIZE_FOR_SIZE | |
10 | select HAVE_GENERIC_HARDIRQS | |
11 | select GENERIC_IRQ_PROBE | |
12 | select GENERIC_PENDING_IRQ if SMP | |
61a16741 | 13 | select GENERIC_IRQ_SHOW |
e6d9668e | 14 | select HAVE_SYSCALL_WRAPPERS if TILEGX |
f133ecca | 15 | select SYS_HYPERVISOR |
8d695143 | 16 | select ARCH_HAVE_NMI_SAFE_CMPXCHG |
867e359b | 17 | |
8df27406 TG |
18 | # FIXME: investigate whether we need/want these options. |
19 | # select HAVE_IOREMAP_PROT | |
5fb682b0 CM |
20 | # select HAVE_OPTPROBES |
21 | # select HAVE_REGS_AND_STACK_ACCESS_API | |
22 | # select HAVE_HW_BREAKPOINT | |
23 | # select PERF_EVENTS | |
24 | # select HAVE_USER_RETURN_NOTIFIER | |
25 | # config NO_BOOTMEM | |
26 | # config ARCH_SUPPORTS_DEBUG_PAGEALLOC | |
27 | # config HUGETLB_PAGE_SIZE_VARIABLE | |
867e359b | 28 | |
8df27406 | 29 | config MMU |
867e359b CM |
30 | def_bool y |
31 | ||
8df27406 | 32 | config GENERIC_CSUM |
867e359b | 33 | def_bool y |
867e359b CM |
34 | |
35 | config SEMAPHORE_SLEEPERS | |
36 | def_bool y | |
37 | ||
38 | config HAVE_ARCH_ALLOC_REMAP | |
39 | def_bool y | |
40 | ||
41 | config HAVE_SETUP_PER_CPU_AREA | |
42 | def_bool y | |
43 | ||
44 | config NEED_PER_CPU_PAGE_FIRST_CHUNK | |
5fb682b0 | 45 | def_bool y |
867e359b CM |
46 | |
47 | config SYS_SUPPORTS_HUGETLBFS | |
48 | def_bool y | |
49 | ||
621b1955 CM |
50 | # Support for additional huge page sizes besides HPAGE_SIZE. |
51 | # The software support is currently only present in the TILE-Gx | |
52 | # hypervisor. TILEPro in any case does not support page sizes | |
53 | # larger than the default HPAGE_SIZE. | |
54 | config HUGETLB_SUPER_PAGES | |
55 | depends on HUGETLB_PAGE && TILEGX | |
56 | def_bool y | |
57 | ||
867e359b CM |
58 | config GENERIC_CLOCKEVENTS |
59 | def_bool y | |
60 | ||
25985edc | 61 | # FIXME: tilegx can implement a more efficient rwsem. |
867e359b CM |
62 | config RWSEM_GENERIC_SPINLOCK |
63 | def_bool y | |
64 | ||
65 | # We have a very flat architecture from a migration point of view, | |
66 | # so save boot time by presetting this (particularly useful on tile-sim). | |
67 | config DEFAULT_MIGRATION_COST | |
68 | int | |
69 | default "10000000" | |
70 | ||
71 | # We only support gcc 4.4 and above, so this should work. | |
72 | config ARCH_SUPPORTS_OPTIMIZED_INLINING | |
73 | def_bool y | |
74 | ||
75 | config ARCH_PHYS_ADDR_T_64BIT | |
76 | def_bool y | |
77 | ||
d31eb519 FT |
78 | config ARCH_DMA_ADDR_T_64BIT |
79 | def_bool y | |
80 | ||
3d1e8a81 CM |
81 | config NEED_DMA_MAP_STATE |
82 | def_bool y | |
83 | ||
867e359b CM |
84 | config LOCKDEP_SUPPORT |
85 | def_bool y | |
86 | ||
87 | config STACKTRACE_SUPPORT | |
88 | def_bool y | |
89 | select STACKTRACE | |
90 | ||
91 | # We use discontigmem for now; at some point we may want to switch | |
92 | # to sparsemem (Tilera bug 7996). | |
93 | config ARCH_DISCONTIGMEM_ENABLE | |
94 | def_bool y | |
95 | ||
96 | config ARCH_DISCONTIGMEM_DEFAULT | |
97 | def_bool y | |
98 | ||
99 | config TRACE_IRQFLAGS_SUPPORT | |
100 | def_bool y | |
101 | ||
102 | config STRICT_DEVMEM | |
103 | def_bool y | |
104 | ||
105 | # SMP is required for Tilera Linux. | |
106 | config SMP | |
107 | def_bool y | |
108 | ||
109 | # Allow checking for compile-time determined overflow errors in | |
110 | # copy_from_user(). There are still unprovable places in the | |
111 | # generic code as of 2.6.34, so this option is not really compatible | |
112 | # with -Werror, which is more useful in general. | |
113 | config DEBUG_COPY_FROM_USER | |
114 | def_bool n | |
115 | ||
116 | config HVC_TILE | |
117 | select HVC_DRIVER | |
118 | def_bool y | |
119 | ||
867e359b | 120 | config TILEGX |
867e359b CM |
121 | bool "Building with TILE-Gx (64-bit) compiler and toolchain" |
122 | ||
acd1a19e CM |
123 | config TILEPRO |
124 | def_bool !TILEGX | |
125 | ||
867e359b | 126 | config 64BIT |
acd1a19e | 127 | def_bool TILEGX |
867e359b CM |
128 | |
129 | config ARCH_DEFCONFIG | |
130 | string | |
3d1e8a81 | 131 | default "arch/tile/configs/tilepro_defconfig" if !TILEGX |
867e359b CM |
132 | default "arch/tile/configs/tilegx_defconfig" if TILEGX |
133 | ||
134 | source "init/Kconfig" | |
135 | ||
136 | menu "Tilera-specific configuration" | |
137 | ||
138 | config NR_CPUS | |
139 | int "Maximum number of tiles (2-255)" | |
140 | range 2 255 | |
141 | depends on SMP | |
142 | default "64" | |
143 | ---help--- | |
144 | Building with 64 is the recommended value, but a slightly | |
145 | smaller kernel memory footprint results from using a smaller | |
146 | value on chips with fewer tiles. | |
147 | ||
d5d14ed6 CM |
148 | if TILEGX |
149 | ||
150 | choice | |
151 | prompt "Kernel page size" | |
152 | default PAGE_SIZE_64KB | |
153 | help | |
154 | This lets you select the page size of the kernel. For best | |
155 | performance on memory-intensive applications, a page size of 64KB | |
156 | is recommended. For workloads involving many small files, many | |
157 | connections, etc., it may be better to select 16KB, which uses | |
158 | memory more efficiently at some cost in TLB performance. | |
159 | ||
160 | Note that this option is TILE-Gx specific; currently | |
161 | TILEPro page size is set by rebuilding the hypervisor. | |
162 | ||
163 | config PAGE_SIZE_16KB | |
164 | bool "16KB" | |
165 | ||
166 | config PAGE_SIZE_64KB | |
167 | bool "64KB" | |
168 | ||
169 | endchoice | |
170 | ||
171 | endif | |
172 | ||
867e359b CM |
173 | source "kernel/time/Kconfig" |
174 | ||
175 | source "kernel/Kconfig.hz" | |
176 | ||
177 | config KEXEC | |
178 | bool "kexec system call" | |
179 | ---help--- | |
180 | kexec is a system call that implements the ability to shutdown your | |
181 | current kernel, and to start another kernel. It is like a reboot | |
182 | but it is independent of the system firmware. It is used | |
183 | to implement the "mboot" Tilera booter. | |
184 | ||
185 | The name comes from the similarity to the exec system call. | |
186 | ||
187 | config COMPAT | |
188 | bool "Support 32-bit TILE-Gx binaries in addition to 64-bit" | |
189 | depends on TILEGX | |
190 | select COMPAT_BINFMT_ELF | |
191 | default y | |
192 | ---help--- | |
193 | If enabled, the kernel will support running TILE-Gx binaries | |
194 | that were built with the -m32 option. | |
195 | ||
196 | config SYSVIPC_COMPAT | |
197 | def_bool y | |
198 | depends on COMPAT && SYSVIPC | |
199 | ||
200 | # We do not currently support disabling HIGHMEM on tile64 and tilepro. | |
201 | config HIGHMEM | |
202 | bool # "Support for more than 512 MB of RAM" | |
203 | default !TILEGX | |
204 | ---help--- | |
205 | Linux can use the full amount of RAM in the system by | |
206 | default. However, the address space of TILE processors is | |
207 | only 4 Gigabytes large. That means that, if you have a large | |
208 | amount of physical memory, not all of it can be "permanently | |
209 | mapped" by the kernel. The physical memory that's not | |
210 | permanently mapped is called "high memory". | |
211 | ||
212 | If you are compiling a kernel which will never run on a | |
213 | machine with more than 512 MB total physical RAM, answer | |
214 | "false" here. This will result in the kernel mapping all of | |
215 | physical memory into the top 1 GB of virtual memory space. | |
216 | ||
217 | If unsure, say "true". | |
218 | ||
219 | # We do not currently support disabling NUMA. | |
220 | config NUMA | |
221 | bool # "NUMA Memory Allocation and Scheduler Support" | |
222 | depends on SMP && DISCONTIGMEM | |
223 | default y | |
224 | ---help--- | |
225 | NUMA memory allocation is required for TILE processors | |
226 | unless booting with memory striping enabled in the | |
227 | hypervisor, or with only a single memory controller. | |
228 | It is recommended that this option always be enabled. | |
229 | ||
230 | config NODES_SHIFT | |
231 | int "Log base 2 of the max number of memory controllers" | |
232 | default 2 | |
233 | depends on NEED_MULTIPLE_NODES | |
234 | ---help--- | |
235 | By default, 2, i.e. 2^2 == 4 DDR2 controllers. | |
236 | In a system with more controllers, this value should be raised. | |
237 | ||
867e359b CM |
238 | choice |
239 | depends on !TILEGX | |
6a108a14 | 240 | prompt "Memory split" if EXPERT |
867e359b CM |
241 | default VMSPLIT_3G |
242 | ---help--- | |
243 | Select the desired split between kernel and user memory. | |
244 | ||
245 | If the address range available to the kernel is less than the | |
246 | physical memory installed, the remaining memory will be available | |
247 | as "high memory". Accessing high memory is a little more costly | |
248 | than low memory, as it needs to be mapped into the kernel first. | |
249 | Note that increasing the kernel address space limits the range | |
250 | available to user programs, making the address space there | |
251 | tighter. Selecting anything other than the default 3G/1G split | |
252 | will also likely make your kernel incompatible with binary-only | |
253 | kernel modules. | |
254 | ||
255 | If you are not absolutely sure what you are doing, leave this | |
256 | option alone! | |
257 | ||
5592840b | 258 | config VMSPLIT_3_75G |
867e359b | 259 | bool "3.75G/0.25G user/kernel split (no kernel networking)" |
5592840b | 260 | config VMSPLIT_3_5G |
867e359b CM |
261 | bool "3.5G/0.5G user/kernel split" |
262 | config VMSPLIT_3G | |
263 | bool "3G/1G user/kernel split" | |
09c17eab CM |
264 | config VMSPLIT_2_75G |
265 | bool "2.75G/1.25G user/kernel split (for full 1G low memory)" | |
266 | config VMSPLIT_2_5G | |
267 | bool "2.5G/1.5G user/kernel split" | |
268 | config VMSPLIT_2_25G | |
269 | bool "2.25G/1.75G user/kernel split" | |
867e359b CM |
270 | config VMSPLIT_2G |
271 | bool "2G/2G user/kernel split" | |
272 | config VMSPLIT_1G | |
273 | bool "1G/3G user/kernel split" | |
274 | endchoice | |
275 | ||
276 | config PAGE_OFFSET | |
277 | hex | |
884197f7 | 278 | depends on !64BIT |
5592840b CM |
279 | default 0xF0000000 if VMSPLIT_3_75G |
280 | default 0xE0000000 if VMSPLIT_3_5G | |
09c17eab CM |
281 | default 0xB0000000 if VMSPLIT_2_75G |
282 | default 0xA0000000 if VMSPLIT_2_5G | |
283 | default 0x90000000 if VMSPLIT_2_25G | |
867e359b CM |
284 | default 0x80000000 if VMSPLIT_2G |
285 | default 0x40000000 if VMSPLIT_1G | |
286 | default 0xC0000000 | |
287 | ||
288 | source "mm/Kconfig" | |
289 | ||
290 | config CMDLINE_BOOL | |
291 | bool "Built-in kernel command line" | |
292 | default n | |
293 | ---help--- | |
294 | Allow for specifying boot arguments to the kernel at | |
295 | build time. On some systems (e.g. embedded ones), it is | |
296 | necessary or convenient to provide some or all of the | |
297 | kernel boot arguments with the kernel itself (that is, | |
298 | to not rely on the boot loader to provide them.) | |
299 | ||
300 | To compile command line arguments into the kernel, | |
301 | set this option to 'Y', then fill in the | |
302 | the boot arguments in CONFIG_CMDLINE. | |
303 | ||
304 | Systems with fully functional boot loaders (e.g. mboot, or | |
305 | if booting over PCI) should leave this option set to 'N'. | |
306 | ||
307 | config CMDLINE | |
308 | string "Built-in kernel command string" | |
309 | depends on CMDLINE_BOOL | |
310 | default "" | |
311 | ---help--- | |
312 | Enter arguments here that should be compiled into the kernel | |
313 | image and used at boot time. If the boot loader provides a | |
314 | command line at boot time, it is appended to this string to | |
315 | form the full kernel command line, when the system boots. | |
316 | ||
317 | However, you can use the CONFIG_CMDLINE_OVERRIDE option to | |
318 | change this behavior. | |
319 | ||
320 | In most cases, the command line (whether built-in or provided | |
321 | by the boot loader) should specify the device for the root | |
322 | file system. | |
323 | ||
324 | config CMDLINE_OVERRIDE | |
325 | bool "Built-in command line overrides boot loader arguments" | |
326 | default n | |
327 | depends on CMDLINE_BOOL | |
328 | ---help--- | |
329 | Set this option to 'Y' to have the kernel ignore the boot loader | |
330 | command line, and use ONLY the built-in command line. | |
331 | ||
332 | This is used to work around broken boot loaders. This should | |
333 | be set to 'N' under normal conditions. | |
334 | ||
335 | config VMALLOC_RESERVE | |
336 | hex | |
337 | default 0x1000000 | |
338 | ||
9f9c0382 CM |
339 | config HARDWALL |
340 | bool "Hardwall support to allow access to user dynamic network" | |
341 | default y | |
342 | ||
a78c942d CM |
343 | config KERNEL_PL |
344 | int "Processor protection level for kernel" | |
345 | range 1 2 | |
346 | default "1" | |
347 | ---help--- | |
348 | This setting determines the processor protection level the | |
349 | kernel will be built to run at. Generally you should use | |
350 | the default value here. | |
351 | ||
867e359b CM |
352 | endmenu # Tilera-specific configuration |
353 | ||
354 | menu "Bus options" | |
355 | ||
f02cbbe6 CM |
356 | config PCI |
357 | bool "PCI support" | |
358 | default y | |
359 | select PCI_DOMAINS | |
84550121 | 360 | select GENERIC_PCI_IOMAP |
f02cbbe6 CM |
361 | ---help--- |
362 | Enable PCI root complex support, so PCIe endpoint devices can | |
363 | be attached to the Tile chip. Many, but not all, PCI devices | |
364 | are supported under Tilera's root complex driver. | |
365 | ||
366 | config PCI_DOMAINS | |
367 | bool | |
368 | ||
867e359b CM |
369 | config NO_IOMEM |
370 | def_bool !PCI | |
371 | ||
372 | config NO_IOPORT | |
373 | def_bool !PCI | |
374 | ||
375 | source "drivers/pci/Kconfig" | |
376 | ||
398fa5a9 CM |
377 | config HOTPLUG |
378 | bool "Support for hot-pluggable devices" | |
379 | ---help--- | |
380 | Say Y here if you want to plug devices into your computer while | |
381 | the system is running, and be able to use them quickly. In many | |
382 | cases, the devices can likewise be unplugged at any time too. | |
383 | One well-known example of this is USB. | |
384 | ||
867e359b CM |
385 | source "drivers/pci/hotplug/Kconfig" |
386 | ||
387 | endmenu | |
388 | ||
389 | menu "Executable file formats" | |
390 | ||
391 | # only elf supported | |
392 | config KCORE_ELF | |
393 | def_bool y | |
394 | depends on PROC_FS | |
395 | ||
396 | source "fs/Kconfig.binfmt" | |
397 | ||
398 | endmenu | |
399 | ||
400 | source "net/Kconfig" | |
401 | ||
402 | source "drivers/Kconfig" | |
403 | ||
404 | source "fs/Kconfig" | |
405 | ||
406 | source "arch/tile/Kconfig.debug" | |
407 | ||
408 | source "security/Kconfig" | |
409 | ||
410 | source "crypto/Kconfig" | |
411 | ||
412 | source "lib/Kconfig" | |
a78c942d CM |
413 | |
414 | source "arch/tile/kvm/Kconfig" |