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
131 bool "Building for TILE-Gx (64-bit) processor"
133 select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
134 select HAVE_FUNCTION_TRACER
135 select HAVE_FUNCTION_GRAPH_TRACER
136 select HAVE_DYNAMIC_FTRACE
137 select HAVE_FTRACE_MCOUNT_RECORD
139 select HAVE_KRETPROBES
140 select HAVE_ARCH_KGDB
141 select ARCH_SUPPORTS_ATOMIC_RMW
149 config ARCH_DEFCONFIG
151 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
152 default "arch/tile/configs/tilegx_defconfig" if TILEGX
154 config PGTABLE_LEVELS
159 source "init/Kconfig"
161 source "kernel/Kconfig.freezer"
163 menu "Tilera-specific configuration"
166 int "Maximum number of tiles (2-255)"
171 Building with 64 is the recommended value, but a slightly
172 smaller kernel memory footprint results from using a smaller
173 value on chips with fewer tiles.
178 prompt "Kernel page size"
179 default PAGE_SIZE_64KB
181 This lets you select the page size of the kernel. For best
182 performance on memory-intensive applications, a page size of 64KB
183 is recommended. For workloads involving many small files, many
184 connections, etc., it may be better to select 16KB, which uses
185 memory more efficiently at some cost in TLB performance.
187 Note that this option is TILE-Gx specific; currently
188 TILEPro page size is set by rebuilding the hypervisor.
190 config PAGE_SIZE_16KB
193 config PAGE_SIZE_64KB
200 source "kernel/Kconfig.hz"
203 bool "kexec system call"
205 kexec is a system call that implements the ability to shutdown your
206 current kernel, and to start another kernel. It is like a reboot
207 but it is independent of the system firmware. It is used
208 to implement the "mboot" Tilera booter.
210 The name comes from the similarity to the exec system call.
213 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
215 select COMPAT_BINFMT_ELF
218 If enabled, the kernel will support running TILE-Gx binaries
219 that were built with the -m32 option.
221 config SYSVIPC_COMPAT
223 depends on COMPAT && SYSVIPC
225 # We do not currently support disabling HIGHMEM on tilepro.
227 bool # "Support for more than 512 MB of RAM"
230 Linux can use the full amount of RAM in the system by
231 default. However, the address space of TILE processors is
232 only 4 Gigabytes large. That means that, if you have a large
233 amount of physical memory, not all of it can be "permanently
234 mapped" by the kernel. The physical memory that's not
235 permanently mapped is called "high memory".
237 If you are compiling a kernel which will never run on a
238 machine with more than 512 MB total physical RAM, answer
239 "false" here. This will result in the kernel mapping all of
240 physical memory into the top 1 GB of virtual memory space.
242 If unsure, say "true".
250 config NEED_SG_DMA_LENGTH
257 select NEED_SG_DMA_LENGTH
258 select ARCH_HAS_DMA_SET_COHERENT_MASK
260 # We do not currently support disabling NUMA.
262 bool # "NUMA Memory Allocation and Scheduler Support"
263 depends on SMP && DISCONTIGMEM
266 NUMA memory allocation is required for TILE processors
267 unless booting with memory striping enabled in the
268 hypervisor, or with only a single memory controller.
269 It is recommended that this option always be enabled.
272 int "Log base 2 of the max number of memory controllers"
274 depends on NEED_MULTIPLE_NODES
276 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
277 In a system with more controllers, this value should be raised.
281 prompt "Memory split" if EXPERT
284 Select the desired split between kernel and user memory.
286 If the address range available to the kernel is less than the
287 physical memory installed, the remaining memory will be available
288 as "high memory". Accessing high memory is a little more costly
289 than low memory, as it needs to be mapped into the kernel first.
290 Note that increasing the kernel address space limits the range
291 available to user programs, making the address space there
292 tighter. Selecting anything other than the default 3G/1G split
293 will also likely make your kernel incompatible with binary-only
296 If you are not absolutely sure what you are doing, leave this
300 bool "3.75G/0.25G user/kernel split (no kernel networking)"
302 bool "3.5G/0.5G user/kernel split"
304 bool "3G/1G user/kernel split"
306 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
308 bool "2.5G/1.5G user/kernel split"
310 bool "2.25G/1.75G user/kernel split"
312 bool "2G/2G user/kernel split"
314 bool "1G/3G user/kernel split"
320 default 0xF0000000 if VMSPLIT_3_75G
321 default 0xE0000000 if VMSPLIT_3_5G
322 default 0xB0000000 if VMSPLIT_2_75G
323 default 0xA0000000 if VMSPLIT_2_5G
324 default 0x90000000 if VMSPLIT_2_25G
325 default 0x80000000 if VMSPLIT_2G
326 default 0x40000000 if VMSPLIT_1G
331 source "kernel/Kconfig.preempt"
334 bool "Built-in kernel command line"
337 Allow for specifying boot arguments to the kernel at
338 build time. On some systems (e.g. embedded ones), it is
339 necessary or convenient to provide some or all of the
340 kernel boot arguments with the kernel itself (that is,
341 to not rely on the boot loader to provide them.)
343 To compile command line arguments into the kernel,
344 set this option to 'Y', then fill in the
345 the boot arguments in CONFIG_CMDLINE.
347 Systems with fully functional boot loaders (e.g. mboot, or
348 if booting over PCI) should leave this option set to 'N'.
351 string "Built-in kernel command string"
352 depends on CMDLINE_BOOL
355 Enter arguments here that should be compiled into the kernel
356 image and used at boot time. If the boot loader provides a
357 command line at boot time, it is appended to this string to
358 form the full kernel command line, when the system boots.
360 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
361 change this behavior.
363 In most cases, the command line (whether built-in or provided
364 by the boot loader) should specify the device for the root
367 config CMDLINE_OVERRIDE
368 bool "Built-in command line overrides boot loader arguments"
370 depends on CMDLINE_BOOL
372 Set this option to 'Y' to have the kernel ignore the boot loader
373 command line, and use ONLY the built-in command line.
375 This is used to work around broken boot loaders. This should
376 be set to 'N' under normal conditions.
378 config VMALLOC_RESERVE
383 bool "Hardwall support to allow access to user dynamic network"
387 int "Processor protection level for kernel"
392 Since MDE 4.2, the Tilera hypervisor runs the kernel
393 at PL2 by default. If running under an older hypervisor,
394 or as a KVM guest, you must run at PL1. (The current
395 hypervisor may also be recompiled with "make HV_PL=2" to
396 allow it to run a kernel at PL1, but clients running at PL1
397 are not expected to be supported indefinitely.)
399 If you're not sure, don't change the default.
401 source "arch/tile/gxio/Kconfig"
403 endmenu # Tilera-specific configuration
411 select GENERIC_PCI_IOMAP
412 select TILE_GXIO_TRIO if TILEGX
413 select PCI_MSI if TILEGX
415 Enable PCI root complex support, so PCIe endpoint devices can
416 be attached to the Tile chip. Many, but not all, PCI devices
417 are supported under Tilera's root complex driver.
429 bool "PCI I/O space support"
434 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
435 is used by few modern PCIe endpoint devices, its support is disabled
436 by default to save the TRIO PIO Region resource for other purposes.
438 source "drivers/pci/Kconfig"
440 source "drivers/pci/pcie/Kconfig"
443 tristate "Tilera USB host adapter support"
447 select TILE_GXIO_USB_HOST
449 Provides USB host adapter support for the built-in EHCI and OHCI
450 interfaces on TILE-Gx chips.
452 source "drivers/pci/hotplug/Kconfig"
456 menu "Executable file formats"
458 source "fs/Kconfig.binfmt"
464 source "drivers/Kconfig"
468 source "arch/tile/Kconfig.debug"
470 source "security/Kconfig"
472 source "crypto/Kconfig"
476 source "arch/tile/kvm/Kconfig"