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
17 select GENERIC_CLOCKEVENTS
19 # FIXME: investigate whether we need/want these options.
20 # select HAVE_IOREMAP_PROT
21 # select HAVE_OPTPROBES
22 # select HAVE_REGS_AND_STACK_ACCESS_API
23 # select HAVE_HW_BREAKPOINT
25 # select HAVE_USER_RETURN_NOTIFIER
27 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
28 # config HUGETLB_PAGE_SIZE_VARIABLE
36 config SEMAPHORE_SLEEPERS
39 config HAVE_ARCH_ALLOC_REMAP
42 config HAVE_SETUP_PER_CPU_AREA
45 config NEED_PER_CPU_PAGE_FIRST_CHUNK
48 config SYS_SUPPORTS_HUGETLBFS
51 # FIXME: tilegx can implement a more efficient rwsem.
52 config RWSEM_GENERIC_SPINLOCK
55 # We have a very flat architecture from a migration point of view,
56 # so save boot time by presetting this (particularly useful on tile-sim).
57 config DEFAULT_MIGRATION_COST
61 # We only support gcc 4.4 and above, so this should work.
62 config ARCH_SUPPORTS_OPTIMIZED_INLINING
65 config ARCH_PHYS_ADDR_T_64BIT
68 config ARCH_DMA_ADDR_T_64BIT
71 config NEED_DMA_MAP_STATE
74 config LOCKDEP_SUPPORT
77 config STACKTRACE_SUPPORT
81 # We use discontigmem for now; at some point we may want to switch
82 # to sparsemem (Tilera bug 7996).
83 config ARCH_DISCONTIGMEM_ENABLE
86 config ARCH_DISCONTIGMEM_DEFAULT
89 config TRACE_IRQFLAGS_SUPPORT
95 # SMP is required for Tilera Linux.
99 # Allow checking for compile-time determined overflow errors in
100 # copy_from_user(). There are still unprovable places in the
101 # generic code as of 2.6.34, so this option is not really compatible
102 # with -Werror, which is more useful in general.
103 config DEBUG_COPY_FROM_USER
110 # Please note: TILE-Gx support is not yet finalized; this is
111 # the preliminary support. TILE-Gx drivers are only provided
112 # with the alpha or beta test versions for Tilera customers.
114 depends on EXPERIMENTAL
115 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
121 config ARCH_DEFCONFIG
123 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
124 default "arch/tile/configs/tilegx_defconfig" if TILEGX
126 source "init/Kconfig"
128 menu "Tilera-specific configuration"
131 int "Maximum number of tiles (2-255)"
136 Building with 64 is the recommended value, but a slightly
137 smaller kernel memory footprint results from using a smaller
138 value on chips with fewer tiles.
140 source "kernel/Kconfig.hz"
143 bool "kexec system call"
145 kexec is a system call that implements the ability to shutdown your
146 current kernel, and to start another kernel. It is like a reboot
147 but it is independent of the system firmware. It is used
148 to implement the "mboot" Tilera booter.
150 The name comes from the similarity to the exec system call.
153 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
155 select COMPAT_BINFMT_ELF
158 If enabled, the kernel will support running TILE-Gx binaries
159 that were built with the -m32 option.
161 config SYSVIPC_COMPAT
163 depends on COMPAT && SYSVIPC
165 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
167 bool # "Support for more than 512 MB of RAM"
170 Linux can use the full amount of RAM in the system by
171 default. However, the address space of TILE processors is
172 only 4 Gigabytes large. That means that, if you have a large
173 amount of physical memory, not all of it can be "permanently
174 mapped" by the kernel. The physical memory that's not
175 permanently mapped is called "high memory".
177 If you are compiling a kernel which will never run on a
178 machine with more than 512 MB total physical RAM, answer
179 "false" here. This will result in the kernel mapping all of
180 physical memory into the top 1 GB of virtual memory space.
182 If unsure, say "true".
184 # We do not currently support disabling NUMA.
186 bool # "NUMA Memory Allocation and Scheduler Support"
187 depends on SMP && DISCONTIGMEM
190 NUMA memory allocation is required for TILE processors
191 unless booting with memory striping enabled in the
192 hypervisor, or with only a single memory controller.
193 It is recommended that this option always be enabled.
196 int "Log base 2 of the max number of memory controllers"
198 depends on NEED_MULTIPLE_NODES
200 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
201 In a system with more controllers, this value should be raised.
205 prompt "Memory split" if EXPERT
208 Select the desired split between kernel and user memory.
210 If the address range available to the kernel is less than the
211 physical memory installed, the remaining memory will be available
212 as "high memory". Accessing high memory is a little more costly
213 than low memory, as it needs to be mapped into the kernel first.
214 Note that increasing the kernel address space limits the range
215 available to user programs, making the address space there
216 tighter. Selecting anything other than the default 3G/1G split
217 will also likely make your kernel incompatible with binary-only
220 If you are not absolutely sure what you are doing, leave this
224 bool "3.75G/0.25G user/kernel split (no kernel networking)"
226 bool "3.5G/0.5G user/kernel split"
228 bool "3G/1G user/kernel split"
230 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
232 bool "2.5G/1.5G user/kernel split"
234 bool "2.25G/1.75G user/kernel split"
236 bool "2G/2G user/kernel split"
238 bool "1G/3G user/kernel split"
244 default 0xF0000000 if VMSPLIT_3_75G
245 default 0xE0000000 if VMSPLIT_3_5G
246 default 0xB0000000 if VMSPLIT_2_75G
247 default 0xA0000000 if VMSPLIT_2_5G
248 default 0x90000000 if VMSPLIT_2_25G
249 default 0x80000000 if VMSPLIT_2G
250 default 0x40000000 if VMSPLIT_1G
256 bool "Built-in kernel command line"
259 Allow for specifying boot arguments to the kernel at
260 build time. On some systems (e.g. embedded ones), it is
261 necessary or convenient to provide some or all of the
262 kernel boot arguments with the kernel itself (that is,
263 to not rely on the boot loader to provide them.)
265 To compile command line arguments into the kernel,
266 set this option to 'Y', then fill in the
267 the boot arguments in CONFIG_CMDLINE.
269 Systems with fully functional boot loaders (e.g. mboot, or
270 if booting over PCI) should leave this option set to 'N'.
273 string "Built-in kernel command string"
274 depends on CMDLINE_BOOL
277 Enter arguments here that should be compiled into the kernel
278 image and used at boot time. If the boot loader provides a
279 command line at boot time, it is appended to this string to
280 form the full kernel command line, when the system boots.
282 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
283 change this behavior.
285 In most cases, the command line (whether built-in or provided
286 by the boot loader) should specify the device for the root
289 config CMDLINE_OVERRIDE
290 bool "Built-in command line overrides boot loader arguments"
292 depends on CMDLINE_BOOL
294 Set this option to 'Y' to have the kernel ignore the boot loader
295 command line, and use ONLY the built-in command line.
297 This is used to work around broken boot loaders. This should
298 be set to 'N' under normal conditions.
300 config VMALLOC_RESERVE
305 bool "Hardwall support to allow access to user dynamic network"
309 int "Processor protection level for kernel"
313 This setting determines the processor protection level the
314 kernel will be built to run at. Generally you should use
315 the default value here.
317 endmenu # Tilera-specific configuration
325 select GENERIC_PCI_IOMAP
327 Enable PCI root complex support, so PCIe endpoint devices can
328 be attached to the Tile chip. Many, but not all, PCI devices
329 are supported under Tilera's root complex driver.
340 source "drivers/pci/Kconfig"
343 bool "Support for hot-pluggable devices"
345 Say Y here if you want to plug devices into your computer while
346 the system is running, and be able to use them quickly. In many
347 cases, the devices can likewise be unplugged at any time too.
348 One well-known example of this is USB.
350 source "drivers/pci/hotplug/Kconfig"
354 menu "Executable file formats"
361 source "fs/Kconfig.binfmt"
367 source "drivers/Kconfig"
371 source "arch/tile/Kconfig.debug"
373 source "security/Kconfig"
375 source "crypto/Kconfig"
379 source "arch/tile/kvm/Kconfig"