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
32 select GENERIC_STRNCPY_FROM_USER
33 select GENERIC_STRNLEN_USER
35 # FIXME: investigate whether we need/want these options.
36 # select HAVE_IOREMAP_PROT
37 # select HAVE_OPTPROBES
38 # select HAVE_REGS_AND_STACK_ACCESS_API
39 # select HAVE_HW_BREAKPOINT
41 # select HAVE_USER_RETURN_NOTIFIER
43 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
44 # config HUGETLB_PAGE_SIZE_VARIABLE
52 config HAVE_ARCH_ALLOC_REMAP
55 config HAVE_SETUP_PER_CPU_AREA
58 config NEED_PER_CPU_PAGE_FIRST_CHUNK
61 config SYS_SUPPORTS_HUGETLBFS
64 # Support for additional huge page sizes besides HPAGE_SIZE.
65 # The software support is currently only present in the TILE-Gx
66 # hypervisor. TILEPro in any case does not support page sizes
67 # larger than the default HPAGE_SIZE.
68 config HUGETLB_SUPER_PAGES
69 depends on HUGETLB_PAGE && TILEGX
72 config GENERIC_TIME_VSYSCALL
75 # Enable PMC if PERF_EVENTS, OPROFILE, or WATCHPOINTS are enabled.
79 # FIXME: tilegx can implement a more efficient rwsem.
80 config RWSEM_GENERIC_SPINLOCK
83 # We only support gcc 4.4 and above, so this should work.
84 config ARCH_SUPPORTS_OPTIMIZED_INLINING
87 config ARCH_PHYS_ADDR_T_64BIT
90 config ARCH_DMA_ADDR_T_64BIT
93 config NEED_DMA_MAP_STATE
96 config ARCH_HAS_DMA_SET_COHERENT_MASK
99 config LOCKDEP_SUPPORT
102 config STACKTRACE_SUPPORT
106 # We use discontigmem for now; at some point we may want to switch
107 # to sparsemem (Tilera bug 7996).
108 config ARCH_DISCONTIGMEM_ENABLE
111 config ARCH_DISCONTIGMEM_DEFAULT
114 config TRACE_IRQFLAGS_SUPPORT
120 # SMP is required for Tilera Linux.
127 select HVC_IRQ if TILEGX
130 # Building with ARCH=tilegx (or ARCH=tile) implies using the
131 # 64-bit TILE-Gx toolchain, so force CONFIG_TILEGX on.
133 def_bool ARCH != "tilepro"
135 select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
136 select HAVE_FUNCTION_TRACER
137 select HAVE_FUNCTION_GRAPH_TRACER
138 select HAVE_DYNAMIC_FTRACE
139 select HAVE_FTRACE_MCOUNT_RECORD
141 select HAVE_KRETPROBES
142 select HAVE_ARCH_KGDB
143 select ARCH_SUPPORTS_ATOMIC_RMW
151 config ARCH_DEFCONFIG
153 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
154 default "arch/tile/configs/tilegx_defconfig" if TILEGX
156 config PGTABLE_LEVELS
161 source "init/Kconfig"
163 source "kernel/Kconfig.freezer"
165 menu "Tilera-specific configuration"
168 int "Maximum number of tiles (2-255)"
173 Building with 64 is the recommended value, but a slightly
174 smaller kernel memory footprint results from using a smaller
175 value on chips with fewer tiles.
180 prompt "Kernel page size"
181 default PAGE_SIZE_64KB
183 This lets you select the page size of the kernel. For best
184 performance on memory-intensive applications, a page size of 64KB
185 is recommended. For workloads involving many small files, many
186 connections, etc., it may be better to select 16KB, which uses
187 memory more efficiently at some cost in TLB performance.
189 Note that this option is TILE-Gx specific; currently
190 TILEPro page size is set by rebuilding the hypervisor.
192 config PAGE_SIZE_16KB
195 config PAGE_SIZE_64KB
202 source "kernel/Kconfig.hz"
205 bool "kexec system call"
207 kexec is a system call that implements the ability to shutdown your
208 current kernel, and to start another kernel. It is like a reboot
209 but it is independent of the system firmware. It is used
210 to implement the "mboot" Tilera booter.
212 The name comes from the similarity to the exec system call.
215 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
217 select COMPAT_BINFMT_ELF
220 If enabled, the kernel will support running TILE-Gx binaries
221 that were built with the -m32 option.
223 config SYSVIPC_COMPAT
225 depends on COMPAT && SYSVIPC
227 # We do not currently support disabling HIGHMEM on tilepro.
229 bool # "Support for more than 512 MB of RAM"
232 Linux can use the full amount of RAM in the system by
233 default. However, the address space of TILE processors is
234 only 4 Gigabytes large. That means that, if you have a large
235 amount of physical memory, not all of it can be "permanently
236 mapped" by the kernel. The physical memory that's not
237 permanently mapped is called "high memory".
239 If you are compiling a kernel which will never run on a
240 machine with more than 512 MB total physical RAM, answer
241 "false" here. This will result in the kernel mapping all of
242 physical memory into the top 1 GB of virtual memory space.
244 If unsure, say "true".
252 config NEED_SG_DMA_LENGTH
259 select NEED_SG_DMA_LENGTH
260 select ARCH_HAS_DMA_SET_COHERENT_MASK
262 # We do not currently support disabling NUMA.
264 bool # "NUMA Memory Allocation and Scheduler Support"
265 depends on SMP && DISCONTIGMEM
268 NUMA memory allocation is required for TILE processors
269 unless booting with memory striping enabled in the
270 hypervisor, or with only a single memory controller.
271 It is recommended that this option always be enabled.
274 int "Log base 2 of the max number of memory controllers"
276 depends on NEED_MULTIPLE_NODES
278 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
279 In a system with more controllers, this value should be raised.
283 prompt "Memory split" if EXPERT
286 Select the desired split between kernel and user memory.
288 If the address range available to the kernel is less than the
289 physical memory installed, the remaining memory will be available
290 as "high memory". Accessing high memory is a little more costly
291 than low memory, as it needs to be mapped into the kernel first.
292 Note that increasing the kernel address space limits the range
293 available to user programs, making the address space there
294 tighter. Selecting anything other than the default 3G/1G split
295 will also likely make your kernel incompatible with binary-only
298 If you are not absolutely sure what you are doing, leave this
302 bool "3.75G/0.25G user/kernel split (no kernel networking)"
304 bool "3.5G/0.5G user/kernel split"
306 bool "3G/1G user/kernel split"
308 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
310 bool "2.5G/1.5G user/kernel split"
312 bool "2.25G/1.75G user/kernel split"
314 bool "2G/2G user/kernel split"
316 bool "1G/3G user/kernel split"
322 default 0xF0000000 if VMSPLIT_3_75G
323 default 0xE0000000 if VMSPLIT_3_5G
324 default 0xB0000000 if VMSPLIT_2_75G
325 default 0xA0000000 if VMSPLIT_2_5G
326 default 0x90000000 if VMSPLIT_2_25G
327 default 0x80000000 if VMSPLIT_2G
328 default 0x40000000 if VMSPLIT_1G
333 source "kernel/Kconfig.preempt"
336 bool "Built-in kernel command line"
339 Allow for specifying boot arguments to the kernel at
340 build time. On some systems (e.g. embedded ones), it is
341 necessary or convenient to provide some or all of the
342 kernel boot arguments with the kernel itself (that is,
343 to not rely on the boot loader to provide them.)
345 To compile command line arguments into the kernel,
346 set this option to 'Y', then fill in the
347 the boot arguments in CONFIG_CMDLINE.
349 Systems with fully functional boot loaders (e.g. mboot, or
350 if booting over PCI) should leave this option set to 'N'.
353 string "Built-in kernel command string"
354 depends on CMDLINE_BOOL
357 Enter arguments here that should be compiled into the kernel
358 image and used at boot time. If the boot loader provides a
359 command line at boot time, it is appended to this string to
360 form the full kernel command line, when the system boots.
362 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
363 change this behavior.
365 In most cases, the command line (whether built-in or provided
366 by the boot loader) should specify the device for the root
369 config CMDLINE_OVERRIDE
370 bool "Built-in command line overrides boot loader arguments"
372 depends on CMDLINE_BOOL
374 Set this option to 'Y' to have the kernel ignore the boot loader
375 command line, and use ONLY the built-in command line.
377 This is used to work around broken boot loaders. This should
378 be set to 'N' under normal conditions.
380 config VMALLOC_RESERVE
385 bool "Hardwall support to allow access to user dynamic network"
389 int "Processor protection level for kernel"
394 Since MDE 4.2, the Tilera hypervisor runs the kernel
395 at PL2 by default. If running under an older hypervisor,
396 or as a KVM guest, you must run at PL1. (The current
397 hypervisor may also be recompiled with "make HV_PL=2" to
398 allow it to run a kernel at PL1, but clients running at PL1
399 are not expected to be supported indefinitely.)
401 If you're not sure, don't change the default.
403 source "arch/tile/gxio/Kconfig"
405 endmenu # Tilera-specific configuration
413 select GENERIC_PCI_IOMAP
414 select TILE_GXIO_TRIO if TILEGX
415 select PCI_MSI if TILEGX
417 Enable PCI root complex support, so PCIe endpoint devices can
418 be attached to the Tile chip. Many, but not all, PCI devices
419 are supported under Tilera's root complex driver.
431 bool "PCI I/O space support"
436 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
437 is used by few modern PCIe endpoint devices, its support is disabled
438 by default to save the TRIO PIO Region resource for other purposes.
440 source "drivers/pci/Kconfig"
442 source "drivers/pci/pcie/Kconfig"
445 tristate "Tilera USB host adapter support"
449 select TILE_GXIO_USB_HOST
451 Provides USB host adapter support for the built-in EHCI and OHCI
452 interfaces on TILE-Gx chips.
454 source "drivers/pci/hotplug/Kconfig"
458 menu "Executable file formats"
460 source "fs/Kconfig.binfmt"
466 source "drivers/Kconfig"
470 source "arch/tile/Kconfig.debug"
472 source "security/Kconfig"
474 source "crypto/Kconfig"
478 source "arch/tile/kvm/Kconfig"