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
28 select HAVE_DEBUG_STACKOVERFLOW
30 # FIXME: investigate whether we need/want these options.
31 # select HAVE_IOREMAP_PROT
32 # select HAVE_OPTPROBES
33 # select HAVE_REGS_AND_STACK_ACCESS_API
34 # select HAVE_HW_BREAKPOINT
36 # select HAVE_USER_RETURN_NOTIFIER
38 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
39 # config HUGETLB_PAGE_SIZE_VARIABLE
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 only support gcc 4.4 and above, so this should work.
72 config ARCH_SUPPORTS_OPTIMIZED_INLINING
75 config ARCH_PHYS_ADDR_T_64BIT
78 config ARCH_DMA_ADDR_T_64BIT
81 config NEED_DMA_MAP_STATE
84 config ARCH_HAS_DMA_SET_COHERENT_MASK
87 config LOCKDEP_SUPPORT
90 config STACKTRACE_SUPPORT
94 # We use discontigmem for now; at some point we may want to switch
95 # to sparsemem (Tilera bug 7996).
96 config ARCH_DISCONTIGMEM_ENABLE
99 config ARCH_DISCONTIGMEM_DEFAULT
102 config TRACE_IRQFLAGS_SUPPORT
108 # SMP is required for Tilera Linux.
115 select HVC_IRQ if TILEGX
119 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
127 config ARCH_DEFCONFIG
129 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
130 default "arch/tile/configs/tilegx_defconfig" if TILEGX
132 source "init/Kconfig"
134 source "kernel/Kconfig.freezer"
136 menu "Tilera-specific configuration"
139 int "Maximum number of tiles (2-255)"
144 Building with 64 is the recommended value, but a slightly
145 smaller kernel memory footprint results from using a smaller
146 value on chips with fewer tiles.
151 prompt "Kernel page size"
152 default PAGE_SIZE_64KB
154 This lets you select the page size of the kernel. For best
155 performance on memory-intensive applications, a page size of 64KB
156 is recommended. For workloads involving many small files, many
157 connections, etc., it may be better to select 16KB, which uses
158 memory more efficiently at some cost in TLB performance.
160 Note that this option is TILE-Gx specific; currently
161 TILEPro page size is set by rebuilding the hypervisor.
163 config PAGE_SIZE_16KB
166 config PAGE_SIZE_64KB
173 source "kernel/Kconfig.hz"
176 bool "kexec system call"
178 kexec is a system call that implements the ability to shutdown your
179 current kernel, and to start another kernel. It is like a reboot
180 but it is independent of the system firmware. It is used
181 to implement the "mboot" Tilera booter.
183 The name comes from the similarity to the exec system call.
186 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
188 select COMPAT_BINFMT_ELF
191 If enabled, the kernel will support running TILE-Gx binaries
192 that were built with the -m32 option.
194 config SYSVIPC_COMPAT
196 depends on COMPAT && SYSVIPC
198 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
200 bool # "Support for more than 512 MB of RAM"
203 Linux can use the full amount of RAM in the system by
204 default. However, the address space of TILE processors is
205 only 4 Gigabytes large. That means that, if you have a large
206 amount of physical memory, not all of it can be "permanently
207 mapped" by the kernel. The physical memory that's not
208 permanently mapped is called "high memory".
210 If you are compiling a kernel which will never run on a
211 machine with more than 512 MB total physical RAM, answer
212 "false" here. This will result in the kernel mapping all of
213 physical memory into the top 1 GB of virtual memory space.
215 If unsure, say "true".
223 config NEED_SG_DMA_LENGTH
230 select NEED_SG_DMA_LENGTH
231 select ARCH_HAS_DMA_SET_COHERENT_MASK
233 # We do not currently support disabling NUMA.
235 bool # "NUMA Memory Allocation and Scheduler Support"
236 depends on SMP && DISCONTIGMEM
239 NUMA memory allocation is required for TILE processors
240 unless booting with memory striping enabled in the
241 hypervisor, or with only a single memory controller.
242 It is recommended that this option always be enabled.
245 int "Log base 2 of the max number of memory controllers"
247 depends on NEED_MULTIPLE_NODES
249 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
250 In a system with more controllers, this value should be raised.
254 prompt "Memory split" if EXPERT
257 Select the desired split between kernel and user memory.
259 If the address range available to the kernel is less than the
260 physical memory installed, the remaining memory will be available
261 as "high memory". Accessing high memory is a little more costly
262 than low memory, as it needs to be mapped into the kernel first.
263 Note that increasing the kernel address space limits the range
264 available to user programs, making the address space there
265 tighter. Selecting anything other than the default 3G/1G split
266 will also likely make your kernel incompatible with binary-only
269 If you are not absolutely sure what you are doing, leave this
273 bool "3.75G/0.25G user/kernel split (no kernel networking)"
275 bool "3.5G/0.5G user/kernel split"
277 bool "3G/1G user/kernel split"
279 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
281 bool "2.5G/1.5G user/kernel split"
283 bool "2.25G/1.75G user/kernel split"
285 bool "2G/2G user/kernel split"
287 bool "1G/3G user/kernel split"
293 default 0xF0000000 if VMSPLIT_3_75G
294 default 0xE0000000 if VMSPLIT_3_5G
295 default 0xB0000000 if VMSPLIT_2_75G
296 default 0xA0000000 if VMSPLIT_2_5G
297 default 0x90000000 if VMSPLIT_2_25G
298 default 0x80000000 if VMSPLIT_2G
299 default 0x40000000 if VMSPLIT_1G
304 source "kernel/Kconfig.preempt"
307 bool "Built-in kernel command line"
310 Allow for specifying boot arguments to the kernel at
311 build time. On some systems (e.g. embedded ones), it is
312 necessary or convenient to provide some or all of the
313 kernel boot arguments with the kernel itself (that is,
314 to not rely on the boot loader to provide them.)
316 To compile command line arguments into the kernel,
317 set this option to 'Y', then fill in the
318 the boot arguments in CONFIG_CMDLINE.
320 Systems with fully functional boot loaders (e.g. mboot, or
321 if booting over PCI) should leave this option set to 'N'.
324 string "Built-in kernel command string"
325 depends on CMDLINE_BOOL
328 Enter arguments here that should be compiled into the kernel
329 image and used at boot time. If the boot loader provides a
330 command line at boot time, it is appended to this string to
331 form the full kernel command line, when the system boots.
333 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
334 change this behavior.
336 In most cases, the command line (whether built-in or provided
337 by the boot loader) should specify the device for the root
340 config CMDLINE_OVERRIDE
341 bool "Built-in command line overrides boot loader arguments"
343 depends on CMDLINE_BOOL
345 Set this option to 'Y' to have the kernel ignore the boot loader
346 command line, and use ONLY the built-in command line.
348 This is used to work around broken boot loaders. This should
349 be set to 'N' under normal conditions.
351 config VMALLOC_RESERVE
356 bool "Hardwall support to allow access to user dynamic network"
360 int "Processor protection level for kernel"
365 Since MDE 4.2, the Tilera hypervisor runs the kernel
366 at PL2 by default. If running under an older hypervisor,
367 or as a KVM guest, you must run at PL1. (The current
368 hypervisor may also be recompiled with "make HV_PL=2" to
369 allow it to run a kernel at PL1, but clients running at PL1
370 are not expected to be supported indefinitely.)
372 If you're not sure, don't change the default.
374 source "arch/tile/gxio/Kconfig"
376 endmenu # Tilera-specific configuration
384 select GENERIC_PCI_IOMAP
385 select TILE_GXIO_TRIO if TILEGX
386 select ARCH_SUPPORTS_MSI if TILEGX
387 select PCI_MSI if TILEGX
389 Enable PCI root complex support, so PCIe endpoint devices can
390 be attached to the Tile chip. Many, but not all, PCI devices
391 are supported under Tilera's root complex driver.
403 bool "PCI I/O space support"
408 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
409 is used by few modern PCIe endpoint devices, its support is disabled
410 by default to save the TRIO PIO Region resource for other purposes.
412 source "drivers/pci/Kconfig"
414 source "drivers/pci/pcie/Kconfig"
417 tristate "Tilera USB host adapter support"
421 select TILE_GXIO_USB_HOST
423 Provides USB host adapter support for the built-in EHCI and OHCI
424 interfaces on TILE-Gx chips.
426 source "drivers/pci/hotplug/Kconfig"
430 menu "Executable file formats"
432 source "fs/Kconfig.binfmt"
438 source "drivers/Kconfig"
442 source "arch/tile/Kconfig.debug"
444 source "security/Kconfig"
446 source "crypto/Kconfig"
450 source "arch/tile/kvm/Kconfig"