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