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.
142 source "kernel/time/Kconfig"
144 source "kernel/Kconfig.hz"
147 bool "kexec system call"
149 kexec is a system call that implements the ability to shutdown your
150 current kernel, and to start another kernel. It is like a reboot
151 but it is independent of the system firmware. It is used
152 to implement the "mboot" Tilera booter.
154 The name comes from the similarity to the exec system call.
157 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
159 select COMPAT_BINFMT_ELF
162 If enabled, the kernel will support running TILE-Gx binaries
163 that were built with the -m32 option.
165 config SYSVIPC_COMPAT
167 depends on COMPAT && SYSVIPC
169 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
171 bool # "Support for more than 512 MB of RAM"
174 Linux can use the full amount of RAM in the system by
175 default. However, the address space of TILE processors is
176 only 4 Gigabytes large. That means that, if you have a large
177 amount of physical memory, not all of it can be "permanently
178 mapped" by the kernel. The physical memory that's not
179 permanently mapped is called "high memory".
181 If you are compiling a kernel which will never run on a
182 machine with more than 512 MB total physical RAM, answer
183 "false" here. This will result in the kernel mapping all of
184 physical memory into the top 1 GB of virtual memory space.
186 If unsure, say "true".
188 # We do not currently support disabling NUMA.
190 bool # "NUMA Memory Allocation and Scheduler Support"
191 depends on SMP && DISCONTIGMEM
194 NUMA memory allocation is required for TILE processors
195 unless booting with memory striping enabled in the
196 hypervisor, or with only a single memory controller.
197 It is recommended that this option always be enabled.
200 int "Log base 2 of the max number of memory controllers"
202 depends on NEED_MULTIPLE_NODES
204 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
205 In a system with more controllers, this value should be raised.
209 prompt "Memory split" if EXPERT
212 Select the desired split between kernel and user memory.
214 If the address range available to the kernel is less than the
215 physical memory installed, the remaining memory will be available
216 as "high memory". Accessing high memory is a little more costly
217 than low memory, as it needs to be mapped into the kernel first.
218 Note that increasing the kernel address space limits the range
219 available to user programs, making the address space there
220 tighter. Selecting anything other than the default 3G/1G split
221 will also likely make your kernel incompatible with binary-only
224 If you are not absolutely sure what you are doing, leave this
228 bool "3.75G/0.25G user/kernel split (no kernel networking)"
230 bool "3.5G/0.5G user/kernel split"
232 bool "3G/1G user/kernel split"
234 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
236 bool "2.5G/1.5G user/kernel split"
238 bool "2.25G/1.75G user/kernel split"
240 bool "2G/2G user/kernel split"
242 bool "1G/3G user/kernel split"
248 default 0xF0000000 if VMSPLIT_3_75G
249 default 0xE0000000 if VMSPLIT_3_5G
250 default 0xB0000000 if VMSPLIT_2_75G
251 default 0xA0000000 if VMSPLIT_2_5G
252 default 0x90000000 if VMSPLIT_2_25G
253 default 0x80000000 if VMSPLIT_2G
254 default 0x40000000 if VMSPLIT_1G
260 bool "Built-in kernel command line"
263 Allow for specifying boot arguments to the kernel at
264 build time. On some systems (e.g. embedded ones), it is
265 necessary or convenient to provide some or all of the
266 kernel boot arguments with the kernel itself (that is,
267 to not rely on the boot loader to provide them.)
269 To compile command line arguments into the kernel,
270 set this option to 'Y', then fill in the
271 the boot arguments in CONFIG_CMDLINE.
273 Systems with fully functional boot loaders (e.g. mboot, or
274 if booting over PCI) should leave this option set to 'N'.
277 string "Built-in kernel command string"
278 depends on CMDLINE_BOOL
281 Enter arguments here that should be compiled into the kernel
282 image and used at boot time. If the boot loader provides a
283 command line at boot time, it is appended to this string to
284 form the full kernel command line, when the system boots.
286 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
287 change this behavior.
289 In most cases, the command line (whether built-in or provided
290 by the boot loader) should specify the device for the root
293 config CMDLINE_OVERRIDE
294 bool "Built-in command line overrides boot loader arguments"
296 depends on CMDLINE_BOOL
298 Set this option to 'Y' to have the kernel ignore the boot loader
299 command line, and use ONLY the built-in command line.
301 This is used to work around broken boot loaders. This should
302 be set to 'N' under normal conditions.
304 config VMALLOC_RESERVE
309 bool "Hardwall support to allow access to user dynamic network"
313 int "Processor protection level for kernel"
317 This setting determines the processor protection level the
318 kernel will be built to run at. Generally you should use
319 the default value here.
321 endmenu # Tilera-specific configuration
329 select GENERIC_PCI_IOMAP
331 Enable PCI root complex support, so PCIe endpoint devices can
332 be attached to the Tile chip. Many, but not all, PCI devices
333 are supported under Tilera's root complex driver.
344 source "drivers/pci/Kconfig"
347 bool "Support for hot-pluggable devices"
349 Say Y here if you want to plug devices into your computer while
350 the system is running, and be able to use them quickly. In many
351 cases, the devices can likewise be unplugged at any time too.
352 One well-known example of this is USB.
354 source "drivers/pci/hotplug/Kconfig"
358 menu "Executable file formats"
365 source "fs/Kconfig.binfmt"
371 source "drivers/Kconfig"
375 source "arch/tile/Kconfig.debug"
377 source "security/Kconfig"
379 source "crypto/Kconfig"
383 source "arch/tile/kvm/Kconfig"