1 # For a description of the syntax of this configuration file,
2 # see Documentation/kbuild/kconfig-language.txt.
7 select HAVE_DMA_API_DEBUG
8 select HAVE_KVM if !TILEGX
9 select GENERIC_FIND_FIRST_BIT
10 select SYSCTL_EXCEPTION_TRACE
11 select USE_GENERIC_SMP_HELPERS
12 select CC_OPTIMIZE_FOR_SIZE
13 select HAVE_DEBUG_KMEMLEAK
14 select HAVE_GENERIC_HARDIRQS
15 select GENERIC_IRQ_PROBE
16 select GENERIC_PENDING_IRQ if SMP
17 select GENERIC_IRQ_SHOW
18 select HAVE_DEBUG_BUGVERBOSE
19 select HAVE_SYSCALL_WRAPPERS if TILEGX
22 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
23 select ARCH_HAVE_NMI_SAFE_CMPXCHG
24 select GENERIC_CLOCKEVENTS
25 select MODULES_USE_ELF_RELA
27 # FIXME: investigate whether we need/want these options.
28 # select HAVE_IOREMAP_PROT
29 # select HAVE_OPTPROBES
30 # select HAVE_REGS_AND_STACK_ACCESS_API
31 # select HAVE_HW_BREAKPOINT
33 # select HAVE_USER_RETURN_NOTIFIER
35 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
36 # config HUGETLB_PAGE_SIZE_VARIABLE
44 config SEMAPHORE_SLEEPERS
47 config HAVE_ARCH_ALLOC_REMAP
50 config HAVE_SETUP_PER_CPU_AREA
53 config NEED_PER_CPU_PAGE_FIRST_CHUNK
56 config SYS_SUPPORTS_HUGETLBFS
59 # Support for additional huge page sizes besides HPAGE_SIZE.
60 # The software support is currently only present in the TILE-Gx
61 # hypervisor. TILEPro in any case does not support page sizes
62 # larger than the default HPAGE_SIZE.
63 config HUGETLB_SUPER_PAGES
64 depends on HUGETLB_PAGE && TILEGX
67 # FIXME: tilegx can implement a more efficient rwsem.
68 config RWSEM_GENERIC_SPINLOCK
71 # We have a very flat architecture from a migration point of view,
72 # so save boot time by presetting this (particularly useful on tile-sim).
73 config DEFAULT_MIGRATION_COST
77 # We only support gcc 4.4 and above, so this should work.
78 config ARCH_SUPPORTS_OPTIMIZED_INLINING
81 config ARCH_PHYS_ADDR_T_64BIT
84 config ARCH_DMA_ADDR_T_64BIT
87 config NEED_DMA_MAP_STATE
90 config ARCH_HAS_DMA_SET_COHERENT_MASK
93 config LOCKDEP_SUPPORT
96 config STACKTRACE_SUPPORT
100 # We use discontigmem for now; at some point we may want to switch
101 # to sparsemem (Tilera bug 7996).
102 config ARCH_DISCONTIGMEM_ENABLE
105 config ARCH_DISCONTIGMEM_DEFAULT
108 config TRACE_IRQFLAGS_SUPPORT
114 # SMP is required for Tilera Linux.
124 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
132 config ARCH_DEFCONFIG
134 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
135 default "arch/tile/configs/tilegx_defconfig" if TILEGX
137 source "init/Kconfig"
139 source "kernel/Kconfig.freezer"
141 menu "Tilera-specific configuration"
144 int "Maximum number of tiles (2-255)"
149 Building with 64 is the recommended value, but a slightly
150 smaller kernel memory footprint results from using a smaller
151 value on chips with fewer tiles.
156 prompt "Kernel page size"
157 default PAGE_SIZE_64KB
159 This lets you select the page size of the kernel. For best
160 performance on memory-intensive applications, a page size of 64KB
161 is recommended. For workloads involving many small files, many
162 connections, etc., it may be better to select 16KB, which uses
163 memory more efficiently at some cost in TLB performance.
165 Note that this option is TILE-Gx specific; currently
166 TILEPro page size is set by rebuilding the hypervisor.
168 config PAGE_SIZE_16KB
171 config PAGE_SIZE_64KB
178 source "kernel/Kconfig.hz"
181 bool "kexec system call"
183 kexec is a system call that implements the ability to shutdown your
184 current kernel, and to start another kernel. It is like a reboot
185 but it is independent of the system firmware. It is used
186 to implement the "mboot" Tilera booter.
188 The name comes from the similarity to the exec system call.
191 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
193 select COMPAT_BINFMT_ELF
196 If enabled, the kernel will support running TILE-Gx binaries
197 that were built with the -m32 option.
199 config SYSVIPC_COMPAT
201 depends on COMPAT && SYSVIPC
203 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
205 bool # "Support for more than 512 MB of RAM"
208 Linux can use the full amount of RAM in the system by
209 default. However, the address space of TILE processors is
210 only 4 Gigabytes large. That means that, if you have a large
211 amount of physical memory, not all of it can be "permanently
212 mapped" by the kernel. The physical memory that's not
213 permanently mapped is called "high memory".
215 If you are compiling a kernel which will never run on a
216 machine with more than 512 MB total physical RAM, answer
217 "false" here. This will result in the kernel mapping all of
218 physical memory into the top 1 GB of virtual memory space.
220 If unsure, say "true".
228 config NEED_SG_DMA_LENGTH
235 select NEED_SG_DMA_LENGTH
236 select ARCH_HAS_DMA_SET_COHERENT_MASK
238 # We do not currently support disabling NUMA.
240 bool # "NUMA Memory Allocation and Scheduler Support"
241 depends on SMP && DISCONTIGMEM
244 NUMA memory allocation is required for TILE processors
245 unless booting with memory striping enabled in the
246 hypervisor, or with only a single memory controller.
247 It is recommended that this option always be enabled.
250 int "Log base 2 of the max number of memory controllers"
252 depends on NEED_MULTIPLE_NODES
254 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
255 In a system with more controllers, this value should be raised.
259 prompt "Memory split" if EXPERT
262 Select the desired split between kernel and user memory.
264 If the address range available to the kernel is less than the
265 physical memory installed, the remaining memory will be available
266 as "high memory". Accessing high memory is a little more costly
267 than low memory, as it needs to be mapped into the kernel first.
268 Note that increasing the kernel address space limits the range
269 available to user programs, making the address space there
270 tighter. Selecting anything other than the default 3G/1G split
271 will also likely make your kernel incompatible with binary-only
274 If you are not absolutely sure what you are doing, leave this
278 bool "3.75G/0.25G user/kernel split (no kernel networking)"
280 bool "3.5G/0.5G user/kernel split"
282 bool "3G/1G user/kernel split"
284 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
286 bool "2.5G/1.5G user/kernel split"
288 bool "2.25G/1.75G user/kernel split"
290 bool "2G/2G user/kernel split"
292 bool "1G/3G user/kernel split"
298 default 0xF0000000 if VMSPLIT_3_75G
299 default 0xE0000000 if VMSPLIT_3_5G
300 default 0xB0000000 if VMSPLIT_2_75G
301 default 0xA0000000 if VMSPLIT_2_5G
302 default 0x90000000 if VMSPLIT_2_25G
303 default 0x80000000 if VMSPLIT_2G
304 default 0x40000000 if VMSPLIT_1G
310 bool "Built-in kernel command line"
313 Allow for specifying boot arguments to the kernel at
314 build time. On some systems (e.g. embedded ones), it is
315 necessary or convenient to provide some or all of the
316 kernel boot arguments with the kernel itself (that is,
317 to not rely on the boot loader to provide them.)
319 To compile command line arguments into the kernel,
320 set this option to 'Y', then fill in the
321 the boot arguments in CONFIG_CMDLINE.
323 Systems with fully functional boot loaders (e.g. mboot, or
324 if booting over PCI) should leave this option set to 'N'.
327 string "Built-in kernel command string"
328 depends on CMDLINE_BOOL
331 Enter arguments here that should be compiled into the kernel
332 image and used at boot time. If the boot loader provides a
333 command line at boot time, it is appended to this string to
334 form the full kernel command line, when the system boots.
336 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
337 change this behavior.
339 In most cases, the command line (whether built-in or provided
340 by the boot loader) should specify the device for the root
343 config CMDLINE_OVERRIDE
344 bool "Built-in command line overrides boot loader arguments"
346 depends on CMDLINE_BOOL
348 Set this option to 'Y' to have the kernel ignore the boot loader
349 command line, and use ONLY the built-in command line.
351 This is used to work around broken boot loaders. This should
352 be set to 'N' under normal conditions.
354 config VMALLOC_RESERVE
359 bool "Hardwall support to allow access to user dynamic network"
363 int "Processor protection level for kernel"
367 This setting determines the processor protection level the
368 kernel will be built to run at. Generally you should use
369 the default value here.
371 source "arch/tile/gxio/Kconfig"
373 endmenu # Tilera-specific configuration
381 select GENERIC_PCI_IOMAP
382 select TILE_GXIO_TRIO if TILEGX
383 select ARCH_SUPPORTS_MSI if TILEGX
384 select PCI_MSI if TILEGX
386 Enable PCI root complex support, so PCIe endpoint devices can
387 be attached to the Tile chip. Many, but not all, PCI devices
388 are supported under Tilera's root complex driver.
399 source "drivers/pci/Kconfig"
402 tristate "Tilera USB host adapter support"
406 select TILE_GXIO_USB_HOST
408 Provides USB host adapter support for the built-in EHCI and OHCI
409 interfaces on TILE-Gx chips.
411 source "drivers/pci/hotplug/Kconfig"
415 menu "Executable file formats"
422 source "fs/Kconfig.binfmt"
428 source "drivers/Kconfig"
432 source "arch/tile/Kconfig.debug"
434 source "security/Kconfig"
436 source "crypto/Kconfig"
440 source "arch/tile/kvm/Kconfig"