1 # For a description of the syntax of this configuration file,
2 # see Documentation/kbuild/kconfig-language.txt.
6 select HAVE_PERF_EVENTS
7 select USE_PMC if PERF_EVENTS
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
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 USER_STACKTRACE_SUPPORT
28 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
29 select HAVE_DEBUG_STACKOVERFLOW
30 select ARCH_WANT_FRAME_POINTERS
31 select HAVE_CONTEXT_TRACKING
33 select GENERIC_STRNCPY_FROM_USER
34 select GENERIC_STRNLEN_USER
35 select HAVE_ARCH_SECCOMP_FILTER
36 select HAVE_ARCH_JUMP_LABEL
38 # FIXME: investigate whether we need/want these options.
39 # select HAVE_IOREMAP_PROT
40 # select HAVE_OPTPROBES
41 # select HAVE_REGS_AND_STACK_ACCESS_API
42 # select HAVE_HW_BREAKPOINT
44 # select HAVE_USER_RETURN_NOTIFIER
46 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
47 # config HUGETLB_PAGE_SIZE_VARIABLE
55 config HAVE_ARCH_ALLOC_REMAP
58 config HAVE_SETUP_PER_CPU_AREA
61 config NEED_PER_CPU_PAGE_FIRST_CHUNK
64 config SYS_SUPPORTS_HUGETLBFS
67 # Support for additional huge page sizes besides HPAGE_SIZE.
68 # The software support is currently only present in the TILE-Gx
69 # hypervisor. TILEPro in any case does not support page sizes
70 # larger than the default HPAGE_SIZE.
71 config HUGETLB_SUPER_PAGES
72 depends on HUGETLB_PAGE && TILEGX
75 config GENERIC_TIME_VSYSCALL
78 # Enable PMC if PERF_EVENTS, OPROFILE, or WATCHPOINTS are enabled.
82 # FIXME: tilegx can implement a more efficient rwsem.
83 config RWSEM_GENERIC_SPINLOCK
86 # We only support gcc 4.4 and above, so this should work.
87 config ARCH_SUPPORTS_OPTIMIZED_INLINING
90 config ARCH_PHYS_ADDR_T_64BIT
93 config ARCH_DMA_ADDR_T_64BIT
96 config NEED_DMA_MAP_STATE
99 config ARCH_HAS_DMA_SET_COHERENT_MASK
102 config LOCKDEP_SUPPORT
105 config STACKTRACE_SUPPORT
109 # We use discontigmem for now; at some point we may want to switch
110 # to sparsemem (Tilera bug 7996).
111 config ARCH_DISCONTIGMEM_ENABLE
114 config ARCH_DISCONTIGMEM_DEFAULT
117 config TRACE_IRQFLAGS_SUPPORT
123 # SMP is required for Tilera Linux.
130 select HVC_IRQ if TILEGX
133 # Building with ARCH=tilegx (or ARCH=tile) implies using the
134 # 64-bit TILE-Gx toolchain, so force CONFIG_TILEGX on.
136 def_bool ARCH != "tilepro"
138 select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
139 select HAVE_FUNCTION_TRACER
140 select HAVE_FUNCTION_GRAPH_TRACER
141 select HAVE_DYNAMIC_FTRACE
142 select HAVE_FTRACE_MCOUNT_RECORD
144 select HAVE_KRETPROBES
145 select HAVE_ARCH_KGDB
146 select ARCH_SUPPORTS_ATOMIC_RMW
154 config ARCH_DEFCONFIG
156 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
157 default "arch/tile/configs/tilegx_defconfig" if TILEGX
159 config PGTABLE_LEVELS
164 source "init/Kconfig"
166 source "kernel/Kconfig.freezer"
168 menu "Tilera-specific configuration"
171 int "Maximum number of tiles (2-255)"
176 Building with 64 is the recommended value, but a slightly
177 smaller kernel memory footprint results from using a smaller
178 value on chips with fewer tiles.
183 prompt "Kernel page size"
184 default PAGE_SIZE_64KB
186 This lets you select the page size of the kernel. For best
187 performance on memory-intensive applications, a page size of 64KB
188 is recommended. For workloads involving many small files, many
189 connections, etc., it may be better to select 16KB, which uses
190 memory more efficiently at some cost in TLB performance.
192 Note that this option is TILE-Gx specific; currently
193 TILEPro page size is set by rebuilding the hypervisor.
195 config PAGE_SIZE_16KB
198 config PAGE_SIZE_64KB
205 source "kernel/Kconfig.hz"
208 bool "kexec system call"
211 kexec is a system call that implements the ability to shutdown your
212 current kernel, and to start another kernel. It is like a reboot
213 but it is independent of the system firmware. It is used
214 to implement the "mboot" Tilera booter.
216 The name comes from the similarity to the exec system call.
219 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
221 select COMPAT_BINFMT_ELF
224 If enabled, the kernel will support running TILE-Gx binaries
225 that were built with the -m32 option.
228 bool "Enable seccomp to safely compute untrusted bytecode"
231 This kernel feature is useful for number crunching applications
232 that may need to compute untrusted bytecode during their
233 execution. By using pipes or other transports made available to
234 the process as file descriptors supporting the read/write
235 syscalls, it's possible to isolate those applications in
236 their own address space using seccomp. Once seccomp is
237 enabled via prctl, it cannot be disabled and the task is only
238 allowed to execute a few safe syscalls defined by each seccomp
243 config SYSVIPC_COMPAT
245 depends on COMPAT && SYSVIPC
247 # We do not currently support disabling HIGHMEM on tilepro.
249 bool # "Support for more than 512 MB of RAM"
252 Linux can use the full amount of RAM in the system by
253 default. However, the address space of TILE processors is
254 only 4 Gigabytes large. That means that, if you have a large
255 amount of physical memory, not all of it can be "permanently
256 mapped" by the kernel. The physical memory that's not
257 permanently mapped is called "high memory".
259 If you are compiling a kernel which will never run on a
260 machine with more than 512 MB total physical RAM, answer
261 "false" here. This will result in the kernel mapping all of
262 physical memory into the top 1 GB of virtual memory space.
264 If unsure, say "true".
272 config NEED_SG_DMA_LENGTH
279 select NEED_SG_DMA_LENGTH
280 select ARCH_HAS_DMA_SET_COHERENT_MASK
282 # We do not currently support disabling NUMA.
284 bool # "NUMA Memory Allocation and Scheduler Support"
285 depends on SMP && DISCONTIGMEM
288 NUMA memory allocation is required for TILE processors
289 unless booting with memory striping enabled in the
290 hypervisor, or with only a single memory controller.
291 It is recommended that this option always be enabled.
294 int "Log base 2 of the max number of memory controllers"
296 depends on NEED_MULTIPLE_NODES
298 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
299 In a system with more controllers, this value should be raised.
303 prompt "Memory split" if EXPERT
306 Select the desired split between kernel and user memory.
308 If the address range available to the kernel is less than the
309 physical memory installed, the remaining memory will be available
310 as "high memory". Accessing high memory is a little more costly
311 than low memory, as it needs to be mapped into the kernel first.
312 Note that increasing the kernel address space limits the range
313 available to user programs, making the address space there
314 tighter. Selecting anything other than the default 3G/1G split
315 will also likely make your kernel incompatible with binary-only
318 If you are not absolutely sure what you are doing, leave this
322 bool "3.75G/0.25G user/kernel split (no kernel networking)"
324 bool "3.5G/0.5G user/kernel split"
326 bool "3G/1G user/kernel split"
328 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
330 bool "2.5G/1.5G user/kernel split"
332 bool "2.25G/1.75G user/kernel split"
334 bool "2G/2G user/kernel split"
336 bool "1G/3G user/kernel split"
342 default 0xF0000000 if VMSPLIT_3_75G
343 default 0xE0000000 if VMSPLIT_3_5G
344 default 0xB0000000 if VMSPLIT_2_75G
345 default 0xA0000000 if VMSPLIT_2_5G
346 default 0x90000000 if VMSPLIT_2_25G
347 default 0x80000000 if VMSPLIT_2G
348 default 0x40000000 if VMSPLIT_1G
353 source "kernel/Kconfig.preempt"
356 bool "Built-in kernel command line"
359 Allow for specifying boot arguments to the kernel at
360 build time. On some systems (e.g. embedded ones), it is
361 necessary or convenient to provide some or all of the
362 kernel boot arguments with the kernel itself (that is,
363 to not rely on the boot loader to provide them.)
365 To compile command line arguments into the kernel,
366 set this option to 'Y', then fill in the
367 the boot arguments in CONFIG_CMDLINE.
369 Systems with fully functional boot loaders (e.g. mboot, or
370 if booting over PCI) should leave this option set to 'N'.
373 string "Built-in kernel command string"
374 depends on CMDLINE_BOOL
377 Enter arguments here that should be compiled into the kernel
378 image and used at boot time. If the boot loader provides a
379 command line at boot time, it is appended to this string to
380 form the full kernel command line, when the system boots.
382 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
383 change this behavior.
385 In most cases, the command line (whether built-in or provided
386 by the boot loader) should specify the device for the root
389 config CMDLINE_OVERRIDE
390 bool "Built-in command line overrides boot loader arguments"
392 depends on CMDLINE_BOOL
394 Set this option to 'Y' to have the kernel ignore the boot loader
395 command line, and use ONLY the built-in command line.
397 This is used to work around broken boot loaders. This should
398 be set to 'N' under normal conditions.
400 config VMALLOC_RESERVE
405 bool "Hardwall support to allow access to user dynamic network"
409 int "Processor protection level for kernel"
414 Since MDE 4.2, the Tilera hypervisor runs the kernel
415 at PL2 by default. If running under an older hypervisor,
416 or as a KVM guest, you must run at PL1. (The current
417 hypervisor may also be recompiled with "make HV_PL=2" to
418 allow it to run a kernel at PL1, but clients running at PL1
419 are not expected to be supported indefinitely.)
421 If you're not sure, don't change the default.
423 source "arch/tile/gxio/Kconfig"
425 endmenu # Tilera-specific configuration
433 select GENERIC_PCI_IOMAP
434 select TILE_GXIO_TRIO if TILEGX
435 select PCI_MSI if TILEGX
437 Enable PCI root complex support, so PCIe endpoint devices can
438 be attached to the Tile chip. Many, but not all, PCI devices
439 are supported under Tilera's root complex driver.
451 bool "PCI I/O space support"
456 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
457 is used by few modern PCIe endpoint devices, its support is disabled
458 by default to save the TRIO PIO Region resource for other purposes.
460 source "drivers/pci/Kconfig"
462 source "drivers/pci/pcie/Kconfig"
465 tristate "Tilera USB host adapter support"
469 select TILE_GXIO_USB_HOST
471 Provides USB host adapter support for the built-in EHCI and OHCI
472 interfaces on TILE-Gx chips.
474 source "drivers/pci/hotplug/Kconfig"
478 menu "Executable file formats"
480 source "fs/Kconfig.binfmt"
486 source "drivers/Kconfig"
490 source "arch/tile/Kconfig.debug"
492 source "security/Kconfig"
494 source "crypto/Kconfig"
498 source "arch/tile/kvm/Kconfig"