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
15 select ARCH_HAVE_NMI_SAFE_CMPXCHG
16 select GENERIC_CLOCKEVENTS
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 # FIXME: tilegx can implement a more efficient rwsem.
51 config RWSEM_GENERIC_SPINLOCK
54 # We have a very flat architecture from a migration point of view,
55 # so save boot time by presetting this (particularly useful on tile-sim).
56 config DEFAULT_MIGRATION_COST
60 # We only support gcc 4.4 and above, so this should work.
61 config ARCH_SUPPORTS_OPTIMIZED_INLINING
64 config ARCH_PHYS_ADDR_T_64BIT
67 config ARCH_DMA_ADDR_T_64BIT
70 config NEED_DMA_MAP_STATE
73 config LOCKDEP_SUPPORT
76 config STACKTRACE_SUPPORT
80 # We use discontigmem for now; at some point we may want to switch
81 # to sparsemem (Tilera bug 7996).
82 config ARCH_DISCONTIGMEM_ENABLE
85 config ARCH_DISCONTIGMEM_DEFAULT
88 config TRACE_IRQFLAGS_SUPPORT
94 # SMP is required for Tilera Linux.
98 # Allow checking for compile-time determined overflow errors in
99 # copy_from_user(). There are still unprovable places in the
100 # generic code as of 2.6.34, so this option is not really compatible
101 # with -Werror, which is more useful in general.
102 config DEBUG_COPY_FROM_USER
109 # Please note: TILE-Gx support is not yet finalized; this is
110 # the preliminary support. TILE-Gx drivers are only provided
111 # with the alpha or beta test versions for Tilera customers.
113 depends on EXPERIMENTAL
114 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
120 config ARCH_DEFCONFIG
122 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
123 default "arch/tile/configs/tilegx_defconfig" if TILEGX
125 source "init/Kconfig"
127 menu "Tilera-specific configuration"
130 int "Maximum number of tiles (2-255)"
135 Building with 64 is the recommended value, but a slightly
136 smaller kernel memory footprint results from using a smaller
137 value on chips with fewer tiles.
139 source "kernel/Kconfig.hz"
142 bool "kexec system call"
144 kexec is a system call that implements the ability to shutdown your
145 current kernel, and to start another kernel. It is like a reboot
146 but it is independent of the system firmware. It is used
147 to implement the "mboot" Tilera booter.
149 The name comes from the similarity to the exec system call.
152 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
154 select COMPAT_BINFMT_ELF
157 If enabled, the kernel will support running TILE-Gx binaries
158 that were built with the -m32 option.
160 config SYSVIPC_COMPAT
162 depends on COMPAT && SYSVIPC
164 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
166 bool # "Support for more than 512 MB of RAM"
169 Linux can use the full amount of RAM in the system by
170 default. However, the address space of TILE processors is
171 only 4 Gigabytes large. That means that, if you have a large
172 amount of physical memory, not all of it can be "permanently
173 mapped" by the kernel. The physical memory that's not
174 permanently mapped is called "high memory".
176 If you are compiling a kernel which will never run on a
177 machine with more than 512 MB total physical RAM, answer
178 "false" here. This will result in the kernel mapping all of
179 physical memory into the top 1 GB of virtual memory space.
181 If unsure, say "true".
183 # We do not currently support disabling NUMA.
185 bool # "NUMA Memory Allocation and Scheduler Support"
186 depends on SMP && DISCONTIGMEM
189 NUMA memory allocation is required for TILE processors
190 unless booting with memory striping enabled in the
191 hypervisor, or with only a single memory controller.
192 It is recommended that this option always be enabled.
195 int "Log base 2 of the max number of memory controllers"
197 depends on NEED_MULTIPLE_NODES
199 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
200 In a system with more controllers, this value should be raised.
204 prompt "Memory split" if EXPERT
207 Select the desired split between kernel and user memory.
209 If the address range available to the kernel is less than the
210 physical memory installed, the remaining memory will be available
211 as "high memory". Accessing high memory is a little more costly
212 than low memory, as it needs to be mapped into the kernel first.
213 Note that increasing the kernel address space limits the range
214 available to user programs, making the address space there
215 tighter. Selecting anything other than the default 3G/1G split
216 will also likely make your kernel incompatible with binary-only
219 If you are not absolutely sure what you are doing, leave this
223 bool "3.75G/0.25G user/kernel split (no kernel networking)"
225 bool "3.5G/0.5G user/kernel split"
227 bool "3G/1G user/kernel split"
229 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
231 bool "2.5G/1.5G user/kernel split"
233 bool "2.25G/1.75G user/kernel split"
235 bool "2G/2G user/kernel split"
237 bool "1G/3G user/kernel split"
243 default 0xF0000000 if VMSPLIT_3_75G
244 default 0xE0000000 if VMSPLIT_3_5G
245 default 0xB0000000 if VMSPLIT_2_75G
246 default 0xA0000000 if VMSPLIT_2_5G
247 default 0x90000000 if VMSPLIT_2_25G
248 default 0x80000000 if VMSPLIT_2G
249 default 0x40000000 if VMSPLIT_1G
255 bool "Built-in kernel command line"
258 Allow for specifying boot arguments to the kernel at
259 build time. On some systems (e.g. embedded ones), it is
260 necessary or convenient to provide some or all of the
261 kernel boot arguments with the kernel itself (that is,
262 to not rely on the boot loader to provide them.)
264 To compile command line arguments into the kernel,
265 set this option to 'Y', then fill in the
266 the boot arguments in CONFIG_CMDLINE.
268 Systems with fully functional boot loaders (e.g. mboot, or
269 if booting over PCI) should leave this option set to 'N'.
272 string "Built-in kernel command string"
273 depends on CMDLINE_BOOL
276 Enter arguments here that should be compiled into the kernel
277 image and used at boot time. If the boot loader provides a
278 command line at boot time, it is appended to this string to
279 form the full kernel command line, when the system boots.
281 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
282 change this behavior.
284 In most cases, the command line (whether built-in or provided
285 by the boot loader) should specify the device for the root
288 config CMDLINE_OVERRIDE
289 bool "Built-in command line overrides boot loader arguments"
291 depends on CMDLINE_BOOL
293 Set this option to 'Y' to have the kernel ignore the boot loader
294 command line, and use ONLY the built-in command line.
296 This is used to work around broken boot loaders. This should
297 be set to 'N' under normal conditions.
299 config VMALLOC_RESERVE
304 bool "Hardwall support to allow access to user dynamic network"
308 int "Processor protection level for kernel"
312 This setting determines the processor protection level the
313 kernel will be built to run at. Generally you should use
314 the default value here.
316 endmenu # Tilera-specific configuration
324 select GENERIC_PCI_IOMAP
326 Enable PCI root complex support, so PCIe endpoint devices can
327 be attached to the Tile chip. Many, but not all, PCI devices
328 are supported under Tilera's root complex driver.
339 source "drivers/pci/Kconfig"
342 bool "Support for hot-pluggable devices"
344 Say Y here if you want to plug devices into your computer while
345 the system is running, and be able to use them quickly. In many
346 cases, the devices can likewise be unplugged at any time too.
347 One well-known example of this is USB.
349 source "drivers/pci/hotplug/Kconfig"
353 menu "Executable file formats"
360 source "fs/Kconfig.binfmt"
366 source "drivers/Kconfig"
370 source "arch/tile/Kconfig.debug"
372 source "security/Kconfig"
374 source "crypto/Kconfig"
378 source "arch/tile/kvm/Kconfig"