1 # For a description of the syntax of this configuration file,
2 # see Documentation/kbuild/kconfig-language.txt.
6 select HAVE_KVM if !TILEGX
7 select GENERIC_FIND_FIRST_BIT
8 select USE_GENERIC_SMP_HELPERS
9 select CC_OPTIMIZE_FOR_SIZE
10 select HAVE_GENERIC_HARDIRQS
11 select GENERIC_IRQ_PROBE
12 select GENERIC_PENDING_IRQ if SMP
13 select GENERIC_IRQ_SHOW
14 select HAVE_SYSCALL_WRAPPERS if TILEGX
16 select ARCH_HAVE_NMI_SAFE_CMPXCHG
18 # FIXME: investigate whether we need/want these options.
19 # select HAVE_IOREMAP_PROT
20 # select HAVE_OPTPROBES
21 # select HAVE_REGS_AND_STACK_ACCESS_API
22 # select HAVE_HW_BREAKPOINT
24 # select HAVE_USER_RETURN_NOTIFIER
26 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
27 # config HUGETLB_PAGE_SIZE_VARIABLE
35 config SEMAPHORE_SLEEPERS
38 config HAVE_ARCH_ALLOC_REMAP
41 config HAVE_SETUP_PER_CPU_AREA
44 config NEED_PER_CPU_PAGE_FIRST_CHUNK
47 config SYS_SUPPORTS_HUGETLBFS
50 config GENERIC_CLOCKEVENTS
53 # FIXME: tilegx can implement a more efficient rwsem.
54 config RWSEM_GENERIC_SPINLOCK
57 # We have a very flat architecture from a migration point of view,
58 # so save boot time by presetting this (particularly useful on tile-sim).
59 config DEFAULT_MIGRATION_COST
63 # We only support gcc 4.4 and above, so this should work.
64 config ARCH_SUPPORTS_OPTIMIZED_INLINING
67 config ARCH_PHYS_ADDR_T_64BIT
70 config ARCH_DMA_ADDR_T_64BIT
73 config NEED_DMA_MAP_STATE
76 config LOCKDEP_SUPPORT
79 config STACKTRACE_SUPPORT
83 # We use discontigmem for now; at some point we may want to switch
84 # to sparsemem (Tilera bug 7996).
85 config ARCH_DISCONTIGMEM_ENABLE
88 config ARCH_DISCONTIGMEM_DEFAULT
91 config TRACE_IRQFLAGS_SUPPORT
97 # SMP is required for Tilera Linux.
101 # Allow checking for compile-time determined overflow errors in
102 # copy_from_user(). There are still unprovable places in the
103 # generic code as of 2.6.34, so this option is not really compatible
104 # with -Werror, which is more useful in general.
105 config DEBUG_COPY_FROM_USER
112 # Please note: TILE-Gx support is not yet finalized; this is
113 # the preliminary support. TILE-Gx drivers are only provided
114 # with the alpha or beta test versions for Tilera customers.
116 depends on EXPERIMENTAL
117 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
123 config ARCH_DEFCONFIG
125 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
126 default "arch/tile/configs/tilegx_defconfig" if TILEGX
128 source "init/Kconfig"
130 menu "Tilera-specific configuration"
133 int "Maximum number of tiles (2-255)"
138 Building with 64 is the recommended value, but a slightly
139 smaller kernel memory footprint results from using a smaller
140 value on chips with fewer tiles.
145 prompt "Kernel page size"
146 default PAGE_SIZE_64KB
148 This lets you select the page size of the kernel. For best
149 performance on memory-intensive applications, a page size of 64KB
150 is recommended. For workloads involving many small files, many
151 connections, etc., it may be better to select 16KB, which uses
152 memory more efficiently at some cost in TLB performance.
154 Note that this option is TILE-Gx specific; currently
155 TILEPro page size is set by rebuilding the hypervisor.
157 config PAGE_SIZE_16KB
160 config PAGE_SIZE_64KB
167 source "kernel/time/Kconfig"
169 source "kernel/Kconfig.hz"
172 bool "kexec system call"
174 kexec is a system call that implements the ability to shutdown your
175 current kernel, and to start another kernel. It is like a reboot
176 but it is independent of the system firmware. It is used
177 to implement the "mboot" Tilera booter.
179 The name comes from the similarity to the exec system call.
182 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
184 select COMPAT_BINFMT_ELF
187 If enabled, the kernel will support running TILE-Gx binaries
188 that were built with the -m32 option.
190 config SYSVIPC_COMPAT
192 depends on COMPAT && SYSVIPC
194 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
196 bool # "Support for more than 512 MB of RAM"
199 Linux can use the full amount of RAM in the system by
200 default. However, the address space of TILE processors is
201 only 4 Gigabytes large. That means that, if you have a large
202 amount of physical memory, not all of it can be "permanently
203 mapped" by the kernel. The physical memory that's not
204 permanently mapped is called "high memory".
206 If you are compiling a kernel which will never run on a
207 machine with more than 512 MB total physical RAM, answer
208 "false" here. This will result in the kernel mapping all of
209 physical memory into the top 1 GB of virtual memory space.
211 If unsure, say "true".
213 # We do not currently support disabling NUMA.
215 bool # "NUMA Memory Allocation and Scheduler Support"
216 depends on SMP && DISCONTIGMEM
219 NUMA memory allocation is required for TILE processors
220 unless booting with memory striping enabled in the
221 hypervisor, or with only a single memory controller.
222 It is recommended that this option always be enabled.
225 int "Log base 2 of the max number of memory controllers"
227 depends on NEED_MULTIPLE_NODES
229 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
230 In a system with more controllers, this value should be raised.
234 prompt "Memory split" if EXPERT
237 Select the desired split between kernel and user memory.
239 If the address range available to the kernel is less than the
240 physical memory installed, the remaining memory will be available
241 as "high memory". Accessing high memory is a little more costly
242 than low memory, as it needs to be mapped into the kernel first.
243 Note that increasing the kernel address space limits the range
244 available to user programs, making the address space there
245 tighter. Selecting anything other than the default 3G/1G split
246 will also likely make your kernel incompatible with binary-only
249 If you are not absolutely sure what you are doing, leave this
253 bool "3.75G/0.25G user/kernel split (no kernel networking)"
255 bool "3.5G/0.5G user/kernel split"
257 bool "3G/1G user/kernel split"
259 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
261 bool "2.5G/1.5G user/kernel split"
263 bool "2.25G/1.75G user/kernel split"
265 bool "2G/2G user/kernel split"
267 bool "1G/3G user/kernel split"
273 default 0xF0000000 if VMSPLIT_3_75G
274 default 0xE0000000 if VMSPLIT_3_5G
275 default 0xB0000000 if VMSPLIT_2_75G
276 default 0xA0000000 if VMSPLIT_2_5G
277 default 0x90000000 if VMSPLIT_2_25G
278 default 0x80000000 if VMSPLIT_2G
279 default 0x40000000 if VMSPLIT_1G
285 bool "Built-in kernel command line"
288 Allow for specifying boot arguments to the kernel at
289 build time. On some systems (e.g. embedded ones), it is
290 necessary or convenient to provide some or all of the
291 kernel boot arguments with the kernel itself (that is,
292 to not rely on the boot loader to provide them.)
294 To compile command line arguments into the kernel,
295 set this option to 'Y', then fill in the
296 the boot arguments in CONFIG_CMDLINE.
298 Systems with fully functional boot loaders (e.g. mboot, or
299 if booting over PCI) should leave this option set to 'N'.
302 string "Built-in kernel command string"
303 depends on CMDLINE_BOOL
306 Enter arguments here that should be compiled into the kernel
307 image and used at boot time. If the boot loader provides a
308 command line at boot time, it is appended to this string to
309 form the full kernel command line, when the system boots.
311 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
312 change this behavior.
314 In most cases, the command line (whether built-in or provided
315 by the boot loader) should specify the device for the root
318 config CMDLINE_OVERRIDE
319 bool "Built-in command line overrides boot loader arguments"
321 depends on CMDLINE_BOOL
323 Set this option to 'Y' to have the kernel ignore the boot loader
324 command line, and use ONLY the built-in command line.
326 This is used to work around broken boot loaders. This should
327 be set to 'N' under normal conditions.
329 config VMALLOC_RESERVE
334 bool "Hardwall support to allow access to user dynamic network"
338 int "Processor protection level for kernel"
342 This setting determines the processor protection level the
343 kernel will be built to run at. Generally you should use
344 the default value here.
346 endmenu # Tilera-specific configuration
354 select GENERIC_PCI_IOMAP
356 Enable PCI root complex support, so PCIe endpoint devices can
357 be attached to the Tile chip. Many, but not all, PCI devices
358 are supported under Tilera's root complex driver.
369 source "drivers/pci/Kconfig"
372 bool "Support for hot-pluggable devices"
374 Say Y here if you want to plug devices into your computer while
375 the system is running, and be able to use them quickly. In many
376 cases, the devices can likewise be unplugged at any time too.
377 One well-known example of this is USB.
379 source "drivers/pci/hotplug/Kconfig"
383 menu "Executable file formats"
390 source "fs/Kconfig.binfmt"
396 source "drivers/Kconfig"
400 source "arch/tile/Kconfig.debug"
402 source "security/Kconfig"
404 source "crypto/Kconfig"
408 source "arch/tile/kvm/Kconfig"