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
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
26 # FIXME: investigate whether we need/want these options.
27 # select HAVE_IOREMAP_PROT
28 # select HAVE_OPTPROBES
29 # select HAVE_REGS_AND_STACK_ACCESS_API
30 # select HAVE_HW_BREAKPOINT
32 # select HAVE_USER_RETURN_NOTIFIER
34 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
35 # config HUGETLB_PAGE_SIZE_VARIABLE
43 config SEMAPHORE_SLEEPERS
46 config HAVE_ARCH_ALLOC_REMAP
49 config HAVE_SETUP_PER_CPU_AREA
52 config NEED_PER_CPU_PAGE_FIRST_CHUNK
55 config SYS_SUPPORTS_HUGETLBFS
58 # Support for additional huge page sizes besides HPAGE_SIZE.
59 # The software support is currently only present in the TILE-Gx
60 # hypervisor. TILEPro in any case does not support page sizes
61 # larger than the default HPAGE_SIZE.
62 config HUGETLB_SUPER_PAGES
63 depends on HUGETLB_PAGE && TILEGX
66 # FIXME: tilegx can implement a more efficient rwsem.
67 config RWSEM_GENERIC_SPINLOCK
70 # We have a very flat architecture from a migration point of view,
71 # so save boot time by presetting this (particularly useful on tile-sim).
72 config DEFAULT_MIGRATION_COST
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
113 # SMP is required for Tilera Linux.
123 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
131 config ARCH_DEFCONFIG
133 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
134 default "arch/tile/configs/tilegx_defconfig" if TILEGX
136 source "init/Kconfig"
138 source "kernel/Kconfig.freezer"
140 menu "Tilera-specific configuration"
143 int "Maximum number of tiles (2-255)"
148 Building with 64 is the recommended value, but a slightly
149 smaller kernel memory footprint results from using a smaller
150 value on chips with fewer tiles.
155 prompt "Kernel page size"
156 default PAGE_SIZE_64KB
158 This lets you select the page size of the kernel. For best
159 performance on memory-intensive applications, a page size of 64KB
160 is recommended. For workloads involving many small files, many
161 connections, etc., it may be better to select 16KB, which uses
162 memory more efficiently at some cost in TLB performance.
164 Note that this option is TILE-Gx specific; currently
165 TILEPro page size is set by rebuilding the hypervisor.
167 config PAGE_SIZE_16KB
170 config PAGE_SIZE_64KB
177 source "kernel/Kconfig.hz"
180 bool "kexec system call"
182 kexec is a system call that implements the ability to shutdown your
183 current kernel, and to start another kernel. It is like a reboot
184 but it is independent of the system firmware. It is used
185 to implement the "mboot" Tilera booter.
187 The name comes from the similarity to the exec system call.
190 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
192 select COMPAT_BINFMT_ELF
195 If enabled, the kernel will support running TILE-Gx binaries
196 that were built with the -m32 option.
198 config SYSVIPC_COMPAT
200 depends on COMPAT && SYSVIPC
202 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
204 bool # "Support for more than 512 MB of RAM"
207 Linux can use the full amount of RAM in the system by
208 default. However, the address space of TILE processors is
209 only 4 Gigabytes large. That means that, if you have a large
210 amount of physical memory, not all of it can be "permanently
211 mapped" by the kernel. The physical memory that's not
212 permanently mapped is called "high memory".
214 If you are compiling a kernel which will never run on a
215 machine with more than 512 MB total physical RAM, answer
216 "false" here. This will result in the kernel mapping all of
217 physical memory into the top 1 GB of virtual memory space.
219 If unsure, say "true".
227 config NEED_SG_DMA_LENGTH
234 select NEED_SG_DMA_LENGTH
235 select ARCH_HAS_DMA_SET_COHERENT_MASK
237 # We do not currently support disabling NUMA.
239 bool # "NUMA Memory Allocation and Scheduler Support"
240 depends on SMP && DISCONTIGMEM
243 NUMA memory allocation is required for TILE processors
244 unless booting with memory striping enabled in the
245 hypervisor, or with only a single memory controller.
246 It is recommended that this option always be enabled.
249 int "Log base 2 of the max number of memory controllers"
251 depends on NEED_MULTIPLE_NODES
253 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
254 In a system with more controllers, this value should be raised.
258 prompt "Memory split" if EXPERT
261 Select the desired split between kernel and user memory.
263 If the address range available to the kernel is less than the
264 physical memory installed, the remaining memory will be available
265 as "high memory". Accessing high memory is a little more costly
266 than low memory, as it needs to be mapped into the kernel first.
267 Note that increasing the kernel address space limits the range
268 available to user programs, making the address space there
269 tighter. Selecting anything other than the default 3G/1G split
270 will also likely make your kernel incompatible with binary-only
273 If you are not absolutely sure what you are doing, leave this
277 bool "3.75G/0.25G user/kernel split (no kernel networking)"
279 bool "3.5G/0.5G user/kernel split"
281 bool "3G/1G user/kernel split"
283 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
285 bool "2.5G/1.5G user/kernel split"
287 bool "2.25G/1.75G user/kernel split"
289 bool "2G/2G user/kernel split"
291 bool "1G/3G user/kernel split"
297 default 0xF0000000 if VMSPLIT_3_75G
298 default 0xE0000000 if VMSPLIT_3_5G
299 default 0xB0000000 if VMSPLIT_2_75G
300 default 0xA0000000 if VMSPLIT_2_5G
301 default 0x90000000 if VMSPLIT_2_25G
302 default 0x80000000 if VMSPLIT_2G
303 default 0x40000000 if VMSPLIT_1G
309 bool "Built-in kernel command line"
312 Allow for specifying boot arguments to the kernel at
313 build time. On some systems (e.g. embedded ones), it is
314 necessary or convenient to provide some or all of the
315 kernel boot arguments with the kernel itself (that is,
316 to not rely on the boot loader to provide them.)
318 To compile command line arguments into the kernel,
319 set this option to 'Y', then fill in the
320 the boot arguments in CONFIG_CMDLINE.
322 Systems with fully functional boot loaders (e.g. mboot, or
323 if booting over PCI) should leave this option set to 'N'.
326 string "Built-in kernel command string"
327 depends on CMDLINE_BOOL
330 Enter arguments here that should be compiled into the kernel
331 image and used at boot time. If the boot loader provides a
332 command line at boot time, it is appended to this string to
333 form the full kernel command line, when the system boots.
335 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
336 change this behavior.
338 In most cases, the command line (whether built-in or provided
339 by the boot loader) should specify the device for the root
342 config CMDLINE_OVERRIDE
343 bool "Built-in command line overrides boot loader arguments"
345 depends on CMDLINE_BOOL
347 Set this option to 'Y' to have the kernel ignore the boot loader
348 command line, and use ONLY the built-in command line.
350 This is used to work around broken boot loaders. This should
351 be set to 'N' under normal conditions.
353 config VMALLOC_RESERVE
358 bool "Hardwall support to allow access to user dynamic network"
362 int "Processor protection level for kernel"
366 This setting determines the processor protection level the
367 kernel will be built to run at. Generally you should use
368 the default value here.
370 source "arch/tile/gxio/Kconfig"
372 endmenu # Tilera-specific configuration
380 select GENERIC_PCI_IOMAP
381 select TILE_GXIO_TRIO if TILEGX
382 select ARCH_SUPPORTS_MSI if TILEGX
383 select PCI_MSI if TILEGX
385 Enable PCI root complex support, so PCIe endpoint devices can
386 be attached to the Tile chip. Many, but not all, PCI devices
387 are supported under Tilera's root complex driver.
398 source "drivers/pci/Kconfig"
401 tristate "Tilera USB host adapter support"
405 select TILE_GXIO_USB_HOST
407 Provides USB host adapter support for the built-in EHCI and OHCI
408 interfaces on TILE-Gx chips.
410 source "drivers/pci/hotplug/Kconfig"
414 menu "Executable file formats"
421 source "fs/Kconfig.binfmt"
427 source "drivers/Kconfig"
431 source "arch/tile/Kconfig.debug"
433 source "security/Kconfig"
435 source "crypto/Kconfig"
439 source "arch/tile/kvm/Kconfig"