1 # For a description of the syntax of this configuration file,
2 # see Documentation/kbuild/kconfig-language.txt.
6 select HAVE_PERF_EVENTS
7 select USE_PMC if PERF_EVENTS
9 select HAVE_DMA_API_DEBUG
10 select HAVE_KVM if !TILEGX
11 select GENERIC_FIND_FIRST_BIT
12 select SYSCTL_EXCEPTION_TRACE
13 select CC_OPTIMIZE_FOR_SIZE
14 select HAVE_DEBUG_KMEMLEAK
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
29 select ARCH_WANT_FRAME_POINTERS
30 select HAVE_CONTEXT_TRACKING
31 select GENERIC_STRNCPY_FROM_USER
32 select GENERIC_STRNLEN_USER
34 # FIXME: investigate whether we need/want these options.
35 # select HAVE_IOREMAP_PROT
36 # select HAVE_OPTPROBES
37 # select HAVE_REGS_AND_STACK_ACCESS_API
38 # select HAVE_HW_BREAKPOINT
40 # select HAVE_USER_RETURN_NOTIFIER
42 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
43 # config HUGETLB_PAGE_SIZE_VARIABLE
51 config HAVE_ARCH_ALLOC_REMAP
54 config HAVE_SETUP_PER_CPU_AREA
57 config NEED_PER_CPU_PAGE_FIRST_CHUNK
60 config SYS_SUPPORTS_HUGETLBFS
63 # Support for additional huge page sizes besides HPAGE_SIZE.
64 # The software support is currently only present in the TILE-Gx
65 # hypervisor. TILEPro in any case does not support page sizes
66 # larger than the default HPAGE_SIZE.
67 config HUGETLB_SUPER_PAGES
68 depends on HUGETLB_PAGE && TILEGX
71 config GENERIC_TIME_VSYSCALL
74 # Enable PMC if PERF_EVENTS, OPROFILE, or WATCHPOINTS are enabled.
78 # FIXME: tilegx can implement a more efficient rwsem.
79 config RWSEM_GENERIC_SPINLOCK
82 # We only support gcc 4.4 and above, so this should work.
83 config ARCH_SUPPORTS_OPTIMIZED_INLINING
86 config ARCH_PHYS_ADDR_T_64BIT
89 config ARCH_DMA_ADDR_T_64BIT
92 config NEED_DMA_MAP_STATE
95 config ARCH_HAS_DMA_SET_COHERENT_MASK
98 config LOCKDEP_SUPPORT
101 config STACKTRACE_SUPPORT
105 # We use discontigmem for now; at some point we may want to switch
106 # to sparsemem (Tilera bug 7996).
107 config ARCH_DISCONTIGMEM_ENABLE
110 config ARCH_DISCONTIGMEM_DEFAULT
113 config TRACE_IRQFLAGS_SUPPORT
119 # SMP is required for Tilera Linux.
126 select HVC_IRQ if TILEGX
130 bool "Building for TILE-Gx (64-bit) processor"
132 select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
133 select HAVE_FUNCTION_TRACER
134 select HAVE_FUNCTION_GRAPH_TRACER
135 select HAVE_DYNAMIC_FTRACE
136 select HAVE_FTRACE_MCOUNT_RECORD
138 select HAVE_KRETPROBES
139 select HAVE_ARCH_KGDB
140 select ARCH_SUPPORTS_ATOMIC_RMW
148 config ARCH_DEFCONFIG
150 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
151 default "arch/tile/configs/tilegx_defconfig" if TILEGX
153 config PGTABLE_LEVELS
158 source "init/Kconfig"
160 source "kernel/Kconfig.freezer"
162 menu "Tilera-specific configuration"
165 int "Maximum number of tiles (2-255)"
170 Building with 64 is the recommended value, but a slightly
171 smaller kernel memory footprint results from using a smaller
172 value on chips with fewer tiles.
177 prompt "Kernel page size"
178 default PAGE_SIZE_64KB
180 This lets you select the page size of the kernel. For best
181 performance on memory-intensive applications, a page size of 64KB
182 is recommended. For workloads involving many small files, many
183 connections, etc., it may be better to select 16KB, which uses
184 memory more efficiently at some cost in TLB performance.
186 Note that this option is TILE-Gx specific; currently
187 TILEPro page size is set by rebuilding the hypervisor.
189 config PAGE_SIZE_16KB
192 config PAGE_SIZE_64KB
199 source "kernel/Kconfig.hz"
202 bool "kexec system call"
204 kexec is a system call that implements the ability to shutdown your
205 current kernel, and to start another kernel. It is like a reboot
206 but it is independent of the system firmware. It is used
207 to implement the "mboot" Tilera booter.
209 The name comes from the similarity to the exec system call.
212 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
214 select COMPAT_BINFMT_ELF
217 If enabled, the kernel will support running TILE-Gx binaries
218 that were built with the -m32 option.
220 config SYSVIPC_COMPAT
222 depends on COMPAT && SYSVIPC
224 # We do not currently support disabling HIGHMEM on tilepro.
226 bool # "Support for more than 512 MB of RAM"
229 Linux can use the full amount of RAM in the system by
230 default. However, the address space of TILE processors is
231 only 4 Gigabytes large. That means that, if you have a large
232 amount of physical memory, not all of it can be "permanently
233 mapped" by the kernel. The physical memory that's not
234 permanently mapped is called "high memory".
236 If you are compiling a kernel which will never run on a
237 machine with more than 512 MB total physical RAM, answer
238 "false" here. This will result in the kernel mapping all of
239 physical memory into the top 1 GB of virtual memory space.
241 If unsure, say "true".
249 config NEED_SG_DMA_LENGTH
256 select NEED_SG_DMA_LENGTH
257 select ARCH_HAS_DMA_SET_COHERENT_MASK
259 # We do not currently support disabling NUMA.
261 bool # "NUMA Memory Allocation and Scheduler Support"
262 depends on SMP && DISCONTIGMEM
265 NUMA memory allocation is required for TILE processors
266 unless booting with memory striping enabled in the
267 hypervisor, or with only a single memory controller.
268 It is recommended that this option always be enabled.
271 int "Log base 2 of the max number of memory controllers"
273 depends on NEED_MULTIPLE_NODES
275 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
276 In a system with more controllers, this value should be raised.
280 prompt "Memory split" if EXPERT
283 Select the desired split between kernel and user memory.
285 If the address range available to the kernel is less than the
286 physical memory installed, the remaining memory will be available
287 as "high memory". Accessing high memory is a little more costly
288 than low memory, as it needs to be mapped into the kernel first.
289 Note that increasing the kernel address space limits the range
290 available to user programs, making the address space there
291 tighter. Selecting anything other than the default 3G/1G split
292 will also likely make your kernel incompatible with binary-only
295 If you are not absolutely sure what you are doing, leave this
299 bool "3.75G/0.25G user/kernel split (no kernel networking)"
301 bool "3.5G/0.5G user/kernel split"
303 bool "3G/1G user/kernel split"
305 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
307 bool "2.5G/1.5G user/kernel split"
309 bool "2.25G/1.75G user/kernel split"
311 bool "2G/2G user/kernel split"
313 bool "1G/3G user/kernel split"
319 default 0xF0000000 if VMSPLIT_3_75G
320 default 0xE0000000 if VMSPLIT_3_5G
321 default 0xB0000000 if VMSPLIT_2_75G
322 default 0xA0000000 if VMSPLIT_2_5G
323 default 0x90000000 if VMSPLIT_2_25G
324 default 0x80000000 if VMSPLIT_2G
325 default 0x40000000 if VMSPLIT_1G
330 source "kernel/Kconfig.preempt"
333 bool "Built-in kernel command line"
336 Allow for specifying boot arguments to the kernel at
337 build time. On some systems (e.g. embedded ones), it is
338 necessary or convenient to provide some or all of the
339 kernel boot arguments with the kernel itself (that is,
340 to not rely on the boot loader to provide them.)
342 To compile command line arguments into the kernel,
343 set this option to 'Y', then fill in the
344 the boot arguments in CONFIG_CMDLINE.
346 Systems with fully functional boot loaders (e.g. mboot, or
347 if booting over PCI) should leave this option set to 'N'.
350 string "Built-in kernel command string"
351 depends on CMDLINE_BOOL
354 Enter arguments here that should be compiled into the kernel
355 image and used at boot time. If the boot loader provides a
356 command line at boot time, it is appended to this string to
357 form the full kernel command line, when the system boots.
359 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
360 change this behavior.
362 In most cases, the command line (whether built-in or provided
363 by the boot loader) should specify the device for the root
366 config CMDLINE_OVERRIDE
367 bool "Built-in command line overrides boot loader arguments"
369 depends on CMDLINE_BOOL
371 Set this option to 'Y' to have the kernel ignore the boot loader
372 command line, and use ONLY the built-in command line.
374 This is used to work around broken boot loaders. This should
375 be set to 'N' under normal conditions.
377 config VMALLOC_RESERVE
382 bool "Hardwall support to allow access to user dynamic network"
386 int "Processor protection level for kernel"
391 Since MDE 4.2, the Tilera hypervisor runs the kernel
392 at PL2 by default. If running under an older hypervisor,
393 or as a KVM guest, you must run at PL1. (The current
394 hypervisor may also be recompiled with "make HV_PL=2" to
395 allow it to run a kernel at PL1, but clients running at PL1
396 are not expected to be supported indefinitely.)
398 If you're not sure, don't change the default.
400 source "arch/tile/gxio/Kconfig"
402 endmenu # Tilera-specific configuration
410 select GENERIC_PCI_IOMAP
411 select TILE_GXIO_TRIO if TILEGX
412 select PCI_MSI if TILEGX
414 Enable PCI root complex support, so PCIe endpoint devices can
415 be attached to the Tile chip. Many, but not all, PCI devices
416 are supported under Tilera's root complex driver.
428 bool "PCI I/O space support"
433 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
434 is used by few modern PCIe endpoint devices, its support is disabled
435 by default to save the TRIO PIO Region resource for other purposes.
437 source "drivers/pci/Kconfig"
439 source "drivers/pci/pcie/Kconfig"
442 tristate "Tilera USB host adapter support"
446 select TILE_GXIO_USB_HOST
448 Provides USB host adapter support for the built-in EHCI and OHCI
449 interfaces on TILE-Gx chips.
451 source "drivers/pci/hotplug/Kconfig"
455 menu "Executable file formats"
457 source "fs/Kconfig.binfmt"
463 source "drivers/Kconfig"
467 source "arch/tile/Kconfig.debug"
469 source "security/Kconfig"
471 source "crypto/Kconfig"
475 source "arch/tile/kvm/Kconfig"