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