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
25 select HAVE_ARCH_TRACEHOOK
26 select HAVE_SYSCALL_TRACEPOINTS
27 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
29 # FIXME: investigate whether we need/want these options.
30 # select HAVE_IOREMAP_PROT
31 # select HAVE_OPTPROBES
32 # select HAVE_REGS_AND_STACK_ACCESS_API
33 # select HAVE_HW_BREAKPOINT
35 # select HAVE_USER_RETURN_NOTIFIER
37 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
38 # config HUGETLB_PAGE_SIZE_VARIABLE
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 only support gcc 4.4 and above, so this should work.
71 config ARCH_SUPPORTS_OPTIMIZED_INLINING
74 config ARCH_PHYS_ADDR_T_64BIT
77 config ARCH_DMA_ADDR_T_64BIT
80 config NEED_DMA_MAP_STATE
83 config ARCH_HAS_DMA_SET_COHERENT_MASK
86 config LOCKDEP_SUPPORT
89 config STACKTRACE_SUPPORT
93 # We use discontigmem for now; at some point we may want to switch
94 # to sparsemem (Tilera bug 7996).
95 config ARCH_DISCONTIGMEM_ENABLE
98 config ARCH_DISCONTIGMEM_DEFAULT
101 config TRACE_IRQFLAGS_SUPPORT
107 # SMP is required for Tilera Linux.
117 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
125 config ARCH_DEFCONFIG
127 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
128 default "arch/tile/configs/tilegx_defconfig" if TILEGX
130 source "init/Kconfig"
132 source "kernel/Kconfig.freezer"
134 menu "Tilera-specific configuration"
137 int "Maximum number of tiles (2-255)"
142 Building with 64 is the recommended value, but a slightly
143 smaller kernel memory footprint results from using a smaller
144 value on chips with fewer tiles.
149 prompt "Kernel page size"
150 default PAGE_SIZE_64KB
152 This lets you select the page size of the kernel. For best
153 performance on memory-intensive applications, a page size of 64KB
154 is recommended. For workloads involving many small files, many
155 connections, etc., it may be better to select 16KB, which uses
156 memory more efficiently at some cost in TLB performance.
158 Note that this option is TILE-Gx specific; currently
159 TILEPro page size is set by rebuilding the hypervisor.
161 config PAGE_SIZE_16KB
164 config PAGE_SIZE_64KB
171 source "kernel/Kconfig.hz"
174 bool "kexec system call"
176 kexec is a system call that implements the ability to shutdown your
177 current kernel, and to start another kernel. It is like a reboot
178 but it is independent of the system firmware. It is used
179 to implement the "mboot" Tilera booter.
181 The name comes from the similarity to the exec system call.
184 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
186 select COMPAT_BINFMT_ELF
189 If enabled, the kernel will support running TILE-Gx binaries
190 that were built with the -m32 option.
192 config SYSVIPC_COMPAT
194 depends on COMPAT && SYSVIPC
196 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
198 bool # "Support for more than 512 MB of RAM"
201 Linux can use the full amount of RAM in the system by
202 default. However, the address space of TILE processors is
203 only 4 Gigabytes large. That means that, if you have a large
204 amount of physical memory, not all of it can be "permanently
205 mapped" by the kernel. The physical memory that's not
206 permanently mapped is called "high memory".
208 If you are compiling a kernel which will never run on a
209 machine with more than 512 MB total physical RAM, answer
210 "false" here. This will result in the kernel mapping all of
211 physical memory into the top 1 GB of virtual memory space.
213 If unsure, say "true".
221 config NEED_SG_DMA_LENGTH
228 select NEED_SG_DMA_LENGTH
229 select ARCH_HAS_DMA_SET_COHERENT_MASK
231 # We do not currently support disabling NUMA.
233 bool # "NUMA Memory Allocation and Scheduler Support"
234 depends on SMP && DISCONTIGMEM
237 NUMA memory allocation is required for TILE processors
238 unless booting with memory striping enabled in the
239 hypervisor, or with only a single memory controller.
240 It is recommended that this option always be enabled.
243 int "Log base 2 of the max number of memory controllers"
245 depends on NEED_MULTIPLE_NODES
247 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
248 In a system with more controllers, this value should be raised.
252 prompt "Memory split" if EXPERT
255 Select the desired split between kernel and user memory.
257 If the address range available to the kernel is less than the
258 physical memory installed, the remaining memory will be available
259 as "high memory". Accessing high memory is a little more costly
260 than low memory, as it needs to be mapped into the kernel first.
261 Note that increasing the kernel address space limits the range
262 available to user programs, making the address space there
263 tighter. Selecting anything other than the default 3G/1G split
264 will also likely make your kernel incompatible with binary-only
267 If you are not absolutely sure what you are doing, leave this
271 bool "3.75G/0.25G user/kernel split (no kernel networking)"
273 bool "3.5G/0.5G user/kernel split"
275 bool "3G/1G user/kernel split"
277 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
279 bool "2.5G/1.5G user/kernel split"
281 bool "2.25G/1.75G user/kernel split"
283 bool "2G/2G user/kernel split"
285 bool "1G/3G user/kernel split"
291 default 0xF0000000 if VMSPLIT_3_75G
292 default 0xE0000000 if VMSPLIT_3_5G
293 default 0xB0000000 if VMSPLIT_2_75G
294 default 0xA0000000 if VMSPLIT_2_5G
295 default 0x90000000 if VMSPLIT_2_25G
296 default 0x80000000 if VMSPLIT_2G
297 default 0x40000000 if VMSPLIT_1G
303 bool "Built-in kernel command line"
306 Allow for specifying boot arguments to the kernel at
307 build time. On some systems (e.g. embedded ones), it is
308 necessary or convenient to provide some or all of the
309 kernel boot arguments with the kernel itself (that is,
310 to not rely on the boot loader to provide them.)
312 To compile command line arguments into the kernel,
313 set this option to 'Y', then fill in the
314 the boot arguments in CONFIG_CMDLINE.
316 Systems with fully functional boot loaders (e.g. mboot, or
317 if booting over PCI) should leave this option set to 'N'.
320 string "Built-in kernel command string"
321 depends on CMDLINE_BOOL
324 Enter arguments here that should be compiled into the kernel
325 image and used at boot time. If the boot loader provides a
326 command line at boot time, it is appended to this string to
327 form the full kernel command line, when the system boots.
329 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
330 change this behavior.
332 In most cases, the command line (whether built-in or provided
333 by the boot loader) should specify the device for the root
336 config CMDLINE_OVERRIDE
337 bool "Built-in command line overrides boot loader arguments"
339 depends on CMDLINE_BOOL
341 Set this option to 'Y' to have the kernel ignore the boot loader
342 command line, and use ONLY the built-in command line.
344 This is used to work around broken boot loaders. This should
345 be set to 'N' under normal conditions.
347 config VMALLOC_RESERVE
352 bool "Hardwall support to allow access to user dynamic network"
356 int "Processor protection level for kernel"
361 Since MDE 4.2, the Tilera hypervisor runs the kernel
362 at PL2 by default. If running under an older hypervisor,
363 or as a KVM guest, you must run at PL1. (The current
364 hypervisor may also be recompiled with "make HV_PL=2" to
365 allow it to run a kernel at PL1, but clients running at PL1
366 are not expected to be supported indefinitely.)
368 If you're not sure, don't change the default.
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"
416 source "fs/Kconfig.binfmt"
422 source "drivers/Kconfig"
426 source "arch/tile/Kconfig.debug"
428 source "security/Kconfig"
430 source "crypto/Kconfig"
434 source "arch/tile/kvm/Kconfig"