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