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 config GENERIC_TIME_VSYSCALL
70 # FIXME: tilegx can implement a more efficient rwsem.
71 config RWSEM_GENERIC_SPINLOCK
74 # We only support gcc 4.4 and above, so this should work.
75 config ARCH_SUPPORTS_OPTIMIZED_INLINING
78 config ARCH_PHYS_ADDR_T_64BIT
81 config ARCH_DMA_ADDR_T_64BIT
84 config NEED_DMA_MAP_STATE
87 config ARCH_HAS_DMA_SET_COHERENT_MASK
90 config LOCKDEP_SUPPORT
93 config STACKTRACE_SUPPORT
97 # We use discontigmem for now; at some point we may want to switch
98 # to sparsemem (Tilera bug 7996).
99 config ARCH_DISCONTIGMEM_ENABLE
102 config ARCH_DISCONTIGMEM_DEFAULT
105 config TRACE_IRQFLAGS_SUPPORT
111 # SMP is required for Tilera Linux.
118 select HVC_IRQ if TILEGX
122 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
130 config ARCH_DEFCONFIG
132 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
133 default "arch/tile/configs/tilegx_defconfig" if TILEGX
135 source "init/Kconfig"
137 source "kernel/Kconfig.freezer"
139 menu "Tilera-specific configuration"
142 int "Maximum number of tiles (2-255)"
147 Building with 64 is the recommended value, but a slightly
148 smaller kernel memory footprint results from using a smaller
149 value on chips with fewer tiles.
154 prompt "Kernel page size"
155 default PAGE_SIZE_64KB
157 This lets you select the page size of the kernel. For best
158 performance on memory-intensive applications, a page size of 64KB
159 is recommended. For workloads involving many small files, many
160 connections, etc., it may be better to select 16KB, which uses
161 memory more efficiently at some cost in TLB performance.
163 Note that this option is TILE-Gx specific; currently
164 TILEPro page size is set by rebuilding the hypervisor.
166 config PAGE_SIZE_16KB
169 config PAGE_SIZE_64KB
176 source "kernel/Kconfig.hz"
179 bool "kexec system call"
181 kexec is a system call that implements the ability to shutdown your
182 current kernel, and to start another kernel. It is like a reboot
183 but it is independent of the system firmware. It is used
184 to implement the "mboot" Tilera booter.
186 The name comes from the similarity to the exec system call.
189 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
191 select COMPAT_BINFMT_ELF
194 If enabled, the kernel will support running TILE-Gx binaries
195 that were built with the -m32 option.
197 config SYSVIPC_COMPAT
199 depends on COMPAT && SYSVIPC
201 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
203 bool # "Support for more than 512 MB of RAM"
206 Linux can use the full amount of RAM in the system by
207 default. However, the address space of TILE processors is
208 only 4 Gigabytes large. That means that, if you have a large
209 amount of physical memory, not all of it can be "permanently
210 mapped" by the kernel. The physical memory that's not
211 permanently mapped is called "high memory".
213 If you are compiling a kernel which will never run on a
214 machine with more than 512 MB total physical RAM, answer
215 "false" here. This will result in the kernel mapping all of
216 physical memory into the top 1 GB of virtual memory space.
218 If unsure, say "true".
226 config NEED_SG_DMA_LENGTH
233 select NEED_SG_DMA_LENGTH
234 select ARCH_HAS_DMA_SET_COHERENT_MASK
236 # We do not currently support disabling NUMA.
238 bool # "NUMA Memory Allocation and Scheduler Support"
239 depends on SMP && DISCONTIGMEM
242 NUMA memory allocation is required for TILE processors
243 unless booting with memory striping enabled in the
244 hypervisor, or with only a single memory controller.
245 It is recommended that this option always be enabled.
248 int "Log base 2 of the max number of memory controllers"
250 depends on NEED_MULTIPLE_NODES
252 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
253 In a system with more controllers, this value should be raised.
257 prompt "Memory split" if EXPERT
260 Select the desired split between kernel and user memory.
262 If the address range available to the kernel is less than the
263 physical memory installed, the remaining memory will be available
264 as "high memory". Accessing high memory is a little more costly
265 than low memory, as it needs to be mapped into the kernel first.
266 Note that increasing the kernel address space limits the range
267 available to user programs, making the address space there
268 tighter. Selecting anything other than the default 3G/1G split
269 will also likely make your kernel incompatible with binary-only
272 If you are not absolutely sure what you are doing, leave this
276 bool "3.75G/0.25G user/kernel split (no kernel networking)"
278 bool "3.5G/0.5G user/kernel split"
280 bool "3G/1G user/kernel split"
282 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
284 bool "2.5G/1.5G user/kernel split"
286 bool "2.25G/1.75G user/kernel split"
288 bool "2G/2G user/kernel split"
290 bool "1G/3G user/kernel split"
296 default 0xF0000000 if VMSPLIT_3_75G
297 default 0xE0000000 if VMSPLIT_3_5G
298 default 0xB0000000 if VMSPLIT_2_75G
299 default 0xA0000000 if VMSPLIT_2_5G
300 default 0x90000000 if VMSPLIT_2_25G
301 default 0x80000000 if VMSPLIT_2G
302 default 0x40000000 if VMSPLIT_1G
307 source "kernel/Kconfig.preempt"
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"
368 Since MDE 4.2, the Tilera hypervisor runs the kernel
369 at PL2 by default. If running under an older hypervisor,
370 or as a KVM guest, you must run at PL1. (The current
371 hypervisor may also be recompiled with "make HV_PL=2" to
372 allow it to run a kernel at PL1, but clients running at PL1
373 are not expected to be supported indefinitely.)
375 If you're not sure, don't change the default.
377 source "arch/tile/gxio/Kconfig"
379 endmenu # Tilera-specific configuration
387 select GENERIC_PCI_IOMAP
388 select TILE_GXIO_TRIO if TILEGX
389 select ARCH_SUPPORTS_MSI if TILEGX
390 select PCI_MSI if TILEGX
392 Enable PCI root complex support, so PCIe endpoint devices can
393 be attached to the Tile chip. Many, but not all, PCI devices
394 are supported under Tilera's root complex driver.
406 bool "PCI I/O space support"
411 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
412 is used by few modern PCIe endpoint devices, its support is disabled
413 by default to save the TRIO PIO Region resource for other purposes.
415 source "drivers/pci/Kconfig"
417 source "drivers/pci/pcie/Kconfig"
420 tristate "Tilera USB host adapter support"
424 select TILE_GXIO_USB_HOST
426 Provides USB host adapter support for the built-in EHCI and OHCI
427 interfaces on TILE-Gx chips.
429 source "drivers/pci/hotplug/Kconfig"
433 menu "Executable file formats"
435 source "fs/Kconfig.binfmt"
441 source "drivers/Kconfig"
445 source "arch/tile/Kconfig.debug"
447 source "security/Kconfig"
449 source "crypto/Kconfig"
453 source "arch/tile/kvm/Kconfig"