1 # For a description of the syntax of this configuration file,
2 # see Documentation/kbuild/kconfig-language.txt.
6 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
7 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
8 select ARCH_HAS_DEVMEM_IS_ALLOWED
9 select ARCH_HAVE_NMI_SAFE_CMPXCHG
10 select ARCH_WANT_FRAME_POINTERS
11 select CC_OPTIMIZE_FOR_SIZE
13 select GENERIC_CLOCKEVENTS
14 select GENERIC_FIND_FIRST_BIT
15 select GENERIC_IRQ_PROBE
16 select GENERIC_IRQ_SHOW
17 select GENERIC_PENDING_IRQ if SMP
18 select GENERIC_STRNCPY_FROM_USER
19 select GENERIC_STRNLEN_USER
20 select HAVE_ARCH_SECCOMP_FILTER
21 select HAVE_ARCH_TRACEHOOK
22 select HAVE_CONTEXT_TRACKING
23 select HAVE_DEBUG_BUGVERBOSE
24 select HAVE_DEBUG_KMEMLEAK
25 select HAVE_DEBUG_STACKOVERFLOW
26 select HAVE_DMA_API_DEBUG
27 select HAVE_EXIT_THREAD
28 select HAVE_KVM if !TILEGX
29 select HAVE_NMI if USE_PMC
30 select HAVE_PERF_EVENTS
31 select HAVE_SYSCALL_TRACEPOINTS
32 select MODULES_USE_ELF_RELA
33 select SYSCTL_EXCEPTION_TRACE
35 select USER_STACKTRACE_SUPPORT
36 select USE_PMC if PERF_EVENTS
45 config HAVE_ARCH_ALLOC_REMAP
48 config HAVE_SETUP_PER_CPU_AREA
51 config NEED_PER_CPU_PAGE_FIRST_CHUNK
54 config SYS_SUPPORTS_HUGETLBFS
57 # Support for additional huge page sizes besides HPAGE_SIZE.
58 # The software support is currently only present in the TILE-Gx
59 # hypervisor. TILEPro in any case does not support page sizes
60 # larger than the default HPAGE_SIZE.
61 config HUGETLB_SUPER_PAGES
62 depends on HUGETLB_PAGE && TILEGX
65 config GENERIC_TIME_VSYSCALL
68 # Enable PMC if PERF_EVENTS, OPROFILE, or WATCHPOINTS are enabled.
72 # FIXME: tilegx can implement a more efficient rwsem.
73 config RWSEM_GENERIC_SPINLOCK
76 # We only support gcc 4.4 and above, so this should work.
77 config ARCH_SUPPORTS_OPTIMIZED_INLINING
80 config ARCH_PHYS_ADDR_T_64BIT
83 config ARCH_DMA_ADDR_T_64BIT
86 config NEED_DMA_MAP_STATE
89 config ARCH_HAS_DMA_SET_COHERENT_MASK
92 config LOCKDEP_SUPPORT
95 config STACKTRACE_SUPPORT
99 # We use discontigmem for now; at some point we may want to switch
100 # to sparsemem (Tilera bug 7996).
101 config ARCH_DISCONTIGMEM_ENABLE
104 config ARCH_DISCONTIGMEM_DEFAULT
107 config TRACE_IRQFLAGS_SUPPORT
110 # SMP is required for Tilera Linux.
117 select HVC_IRQ if TILEGX
120 # Building with ARCH=tilegx (or ARCH=tile) implies using the
121 # 64-bit TILE-Gx toolchain, so force CONFIG_TILEGX on.
123 def_bool ARCH != "tilepro"
124 select ARCH_SUPPORTS_ATOMIC_RMW
125 select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
126 select HAVE_ARCH_JUMP_LABEL
127 select HAVE_ARCH_KGDB
128 select HAVE_DYNAMIC_FTRACE
129 select HAVE_FTRACE_MCOUNT_RECORD
130 select HAVE_FUNCTION_GRAPH_TRACER
131 select HAVE_FUNCTION_TRACER
133 select HAVE_KRETPROBES
142 config ARCH_DEFCONFIG
144 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
145 default "arch/tile/configs/tilegx_defconfig" if TILEGX
147 config PGTABLE_LEVELS
152 source "init/Kconfig"
154 source "kernel/Kconfig.freezer"
156 menu "Tilera-specific configuration"
159 int "Maximum number of tiles (2-255)"
164 Building with 64 is the recommended value, but a slightly
165 smaller kernel memory footprint results from using a smaller
166 value on chips with fewer tiles.
169 prompt "Kernel page size"
170 default PAGE_SIZE_64KB
172 This lets you select the page size of the kernel. For best
173 performance on memory-intensive applications, a page size of 64KB
174 is recommended. For workloads involving many small files, many
175 connections, etc., it may be better to select 16KB, which uses
176 memory more efficiently at some cost in TLB performance.
178 Note that for TILEPro, you must also rebuild the hypervisor
179 with a matching page size.
182 bool "4KB" if TILEPRO
184 config PAGE_SIZE_16KB
187 config PAGE_SIZE_64KB
192 source "kernel/Kconfig.hz"
195 bool "kexec system call"
198 kexec is a system call that implements the ability to shutdown your
199 current kernel, and to start another kernel. It is like a reboot
200 but it is independent of the system firmware. It is used
201 to implement the "mboot" Tilera booter.
203 The name comes from the similarity to the exec system call.
206 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
208 select COMPAT_BINFMT_ELF
211 If enabled, the kernel will support running TILE-Gx binaries
212 that were built with the -m32 option.
215 bool "Enable seccomp to safely compute untrusted bytecode"
218 This kernel feature is useful for number crunching applications
219 that may need to compute untrusted bytecode during their
220 execution. By using pipes or other transports made available to
221 the process as file descriptors supporting the read/write
222 syscalls, it's possible to isolate those applications in
223 their own address space using seccomp. Once seccomp is
224 enabled via prctl, it cannot be disabled and the task is only
225 allowed to execute a few safe syscalls defined by each seccomp
230 config SYSVIPC_COMPAT
232 depends on COMPAT && SYSVIPC
234 # We do not currently support disabling HIGHMEM on tilepro.
236 bool # "Support for more than 512 MB of RAM"
239 Linux can use the full amount of RAM in the system by
240 default. However, the address space of TILE processors is
241 only 4 Gigabytes large. That means that, if you have a large
242 amount of physical memory, not all of it can be "permanently
243 mapped" by the kernel. The physical memory that's not
244 permanently mapped is called "high memory".
246 If you are compiling a kernel which will never run on a
247 machine with more than 512 MB total physical RAM, answer
248 "false" here. This will result in the kernel mapping all of
249 physical memory into the top 1 GB of virtual memory space.
251 If unsure, say "true".
259 config NEED_SG_DMA_LENGTH
266 select NEED_SG_DMA_LENGTH
267 select ARCH_HAS_DMA_SET_COHERENT_MASK
269 # We do not currently support disabling NUMA.
271 bool # "NUMA Memory Allocation and Scheduler Support"
272 depends on SMP && DISCONTIGMEM
275 NUMA memory allocation is required for TILE processors
276 unless booting with memory striping enabled in the
277 hypervisor, or with only a single memory controller.
278 It is recommended that this option always be enabled.
281 int "Log base 2 of the max number of memory controllers"
283 depends on NEED_MULTIPLE_NODES
285 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
286 In a system with more controllers, this value should be raised.
290 prompt "Memory split" if EXPERT
293 Select the desired split between kernel and user memory.
295 If the address range available to the kernel is less than the
296 physical memory installed, the remaining memory will be available
297 as "high memory". Accessing high memory is a little more costly
298 than low memory, as it needs to be mapped into the kernel first.
299 Note that increasing the kernel address space limits the range
300 available to user programs, making the address space there
301 tighter. Selecting anything other than the default 3G/1G split
302 will also likely make your kernel incompatible with binary-only
305 If you are not absolutely sure what you are doing, leave this
309 bool "3.75G/0.25G user/kernel split (no kernel networking)"
311 bool "3.5G/0.5G user/kernel split"
313 bool "3G/1G user/kernel split"
315 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
317 bool "2.5G/1.5G user/kernel split"
319 bool "2.25G/1.75G user/kernel split"
321 bool "2G/2G user/kernel split"
323 bool "1G/3G user/kernel split"
329 default 0xF0000000 if VMSPLIT_3_75G
330 default 0xE0000000 if VMSPLIT_3_5G
331 default 0xB0000000 if VMSPLIT_2_75G
332 default 0xA0000000 if VMSPLIT_2_5G
333 default 0x90000000 if VMSPLIT_2_25G
334 default 0x80000000 if VMSPLIT_2G
335 default 0x40000000 if VMSPLIT_1G
340 source "kernel/Kconfig.preempt"
343 bool "Built-in kernel command line"
346 Allow for specifying boot arguments to the kernel at
347 build time. On some systems (e.g. embedded ones), it is
348 necessary or convenient to provide some or all of the
349 kernel boot arguments with the kernel itself (that is,
350 to not rely on the boot loader to provide them.)
352 To compile command line arguments into the kernel,
353 set this option to 'Y', then fill in the
354 the boot arguments in CONFIG_CMDLINE.
356 Systems with fully functional boot loaders (e.g. mboot, or
357 if booting over PCI) should leave this option set to 'N'.
360 string "Built-in kernel command string"
361 depends on CMDLINE_BOOL
364 Enter arguments here that should be compiled into the kernel
365 image and used at boot time. If the boot loader provides a
366 command line at boot time, it is appended to this string to
367 form the full kernel command line, when the system boots.
369 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
370 change this behavior.
372 In most cases, the command line (whether built-in or provided
373 by the boot loader) should specify the device for the root
376 config CMDLINE_OVERRIDE
377 bool "Built-in command line overrides boot loader arguments"
379 depends on CMDLINE_BOOL
381 Set this option to 'Y' to have the kernel ignore the boot loader
382 command line, and use ONLY the built-in command line.
384 This is used to work around broken boot loaders. This should
385 be set to 'N' under normal conditions.
387 config VMALLOC_RESERVE
392 bool "Hardwall support to allow access to user dynamic network"
396 int "Processor protection level for kernel"
401 Since MDE 4.2, the Tilera hypervisor runs the kernel
402 at PL2 by default. If running under an older hypervisor,
403 or as a KVM guest, you must run at PL1. (The current
404 hypervisor may also be recompiled with "make HV_PL=2" to
405 allow it to run a kernel at PL1, but clients running at PL1
406 are not expected to be supported indefinitely.)
408 If you're not sure, don't change the default.
410 source "arch/tile/gxio/Kconfig"
412 endmenu # Tilera-specific configuration
420 select GENERIC_PCI_IOMAP
421 select TILE_GXIO_TRIO if TILEGX
422 select PCI_MSI if TILEGX
424 Enable PCI root complex support, so PCIe endpoint devices can
425 be attached to the Tile chip. Many, but not all, PCI devices
426 are supported under Tilera's root complex driver.
438 bool "PCI I/O space support"
443 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
444 is used by few modern PCIe endpoint devices, its support is disabled
445 by default to save the TRIO PIO Region resource for other purposes.
447 source "drivers/pci/Kconfig"
450 tristate "Tilera USB host adapter support"
454 select TILE_GXIO_USB_HOST
456 Provides USB host adapter support for the built-in EHCI and OHCI
457 interfaces on TILE-Gx chips.
461 menu "Executable file formats"
463 source "fs/Kconfig.binfmt"
469 source "drivers/Kconfig"
473 source "arch/tile/Kconfig.debug"
475 source "security/Kconfig"
477 source "crypto/Kconfig"
481 source "arch/tile/kvm/Kconfig"