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