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
17 # FIXME: investigate whether we need/want these options.
18 # select HAVE_IOREMAP_PROT
19 # select HAVE_OPTPROBES
20 # select HAVE_REGS_AND_STACK_ACCESS_API
21 # select HAVE_HW_BREAKPOINT
23 # select HAVE_USER_RETURN_NOTIFIER
25 # config ARCH_SUPPORTS_DEBUG_PAGEALLOC
26 # config HUGETLB_PAGE_SIZE_VARIABLE
34 config SEMAPHORE_SLEEPERS
37 config HAVE_ARCH_ALLOC_REMAP
40 config HAVE_SETUP_PER_CPU_AREA
43 config NEED_PER_CPU_PAGE_FIRST_CHUNK
46 config SYS_SUPPORTS_HUGETLBFS
49 config GENERIC_CLOCKEVENTS
52 # FIXME: tilegx can implement a more efficient rwsem.
53 config RWSEM_GENERIC_SPINLOCK
56 # We have a very flat architecture from a migration point of view,
57 # so save boot time by presetting this (particularly useful on tile-sim).
58 config DEFAULT_MIGRATION_COST
62 # We only support gcc 4.4 and above, so this should work.
63 config ARCH_SUPPORTS_OPTIMIZED_INLINING
66 config ARCH_PHYS_ADDR_T_64BIT
69 config ARCH_DMA_ADDR_T_64BIT
72 config NEED_DMA_MAP_STATE
75 config LOCKDEP_SUPPORT
78 config STACKTRACE_SUPPORT
82 # We use discontigmem for now; at some point we may want to switch
83 # to sparsemem (Tilera bug 7996).
84 config ARCH_DISCONTIGMEM_ENABLE
87 config ARCH_DISCONTIGMEM_DEFAULT
90 config TRACE_IRQFLAGS_SUPPORT
96 # SMP is required for Tilera Linux.
100 # Allow checking for compile-time determined overflow errors in
101 # copy_from_user(). There are still unprovable places in the
102 # generic code as of 2.6.34, so this option is not really compatible
103 # with -Werror, which is more useful in general.
104 config DEBUG_COPY_FROM_USER
111 # Please note: TILE-Gx support is not yet finalized; this is
112 # the preliminary support. TILE-Gx drivers are only provided
113 # with the alpha or beta test versions for Tilera customers.
115 depends on EXPERIMENTAL
116 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
122 config ARCH_DEFCONFIG
124 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
125 default "arch/tile/configs/tilegx_defconfig" if TILEGX
127 source "init/Kconfig"
129 menu "Tilera-specific configuration"
132 int "Maximum number of tiles (2-255)"
137 Building with 64 is the recommended value, but a slightly
138 smaller kernel memory footprint results from using a smaller
139 value on chips with fewer tiles.
141 source "kernel/time/Kconfig"
143 source "kernel/Kconfig.hz"
146 bool "kexec system call"
148 kexec is a system call that implements the ability to shutdown your
149 current kernel, and to start another kernel. It is like a reboot
150 but it is independent of the system firmware. It is used
151 to implement the "mboot" Tilera booter.
153 The name comes from the similarity to the exec system call.
156 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
158 select COMPAT_BINFMT_ELF
161 If enabled, the kernel will support running TILE-Gx binaries
162 that were built with the -m32 option.
164 config SYSVIPC_COMPAT
166 depends on COMPAT && SYSVIPC
168 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
170 bool # "Support for more than 512 MB of RAM"
173 Linux can use the full amount of RAM in the system by
174 default. However, the address space of TILE processors is
175 only 4 Gigabytes large. That means that, if you have a large
176 amount of physical memory, not all of it can be "permanently
177 mapped" by the kernel. The physical memory that's not
178 permanently mapped is called "high memory".
180 If you are compiling a kernel which will never run on a
181 machine with more than 512 MB total physical RAM, answer
182 "false" here. This will result in the kernel mapping all of
183 physical memory into the top 1 GB of virtual memory space.
185 If unsure, say "true".
187 # We do not currently support disabling NUMA.
189 bool # "NUMA Memory Allocation and Scheduler Support"
190 depends on SMP && DISCONTIGMEM
193 NUMA memory allocation is required for TILE processors
194 unless booting with memory striping enabled in the
195 hypervisor, or with only a single memory controller.
196 It is recommended that this option always be enabled.
199 int "Log base 2 of the max number of memory controllers"
201 depends on NEED_MULTIPLE_NODES
203 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
204 In a system with more controllers, this value should be raised.
208 prompt "Memory split" if EXPERT
211 Select the desired split between kernel and user memory.
213 If the address range available to the kernel is less than the
214 physical memory installed, the remaining memory will be available
215 as "high memory". Accessing high memory is a little more costly
216 than low memory, as it needs to be mapped into the kernel first.
217 Note that increasing the kernel address space limits the range
218 available to user programs, making the address space there
219 tighter. Selecting anything other than the default 3G/1G split
220 will also likely make your kernel incompatible with binary-only
223 If you are not absolutely sure what you are doing, leave this
227 bool "3.75G/0.25G user/kernel split (no kernel networking)"
229 bool "3.5G/0.5G user/kernel split"
231 bool "3G/1G user/kernel split"
233 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
235 bool "2.5G/1.5G user/kernel split"
237 bool "2.25G/1.75G user/kernel split"
239 bool "2G/2G user/kernel split"
241 bool "1G/3G user/kernel split"
247 default 0xF0000000 if VMSPLIT_3_75G
248 default 0xE0000000 if VMSPLIT_3_5G
249 default 0xB0000000 if VMSPLIT_2_75G
250 default 0xA0000000 if VMSPLIT_2_5G
251 default 0x90000000 if VMSPLIT_2_25G
252 default 0x80000000 if VMSPLIT_2G
253 default 0x40000000 if VMSPLIT_1G
259 bool "Built-in kernel command line"
262 Allow for specifying boot arguments to the kernel at
263 build time. On some systems (e.g. embedded ones), it is
264 necessary or convenient to provide some or all of the
265 kernel boot arguments with the kernel itself (that is,
266 to not rely on the boot loader to provide them.)
268 To compile command line arguments into the kernel,
269 set this option to 'Y', then fill in the
270 the boot arguments in CONFIG_CMDLINE.
272 Systems with fully functional boot loaders (e.g. mboot, or
273 if booting over PCI) should leave this option set to 'N'.
276 string "Built-in kernel command string"
277 depends on CMDLINE_BOOL
280 Enter arguments here that should be compiled into the kernel
281 image and used at boot time. If the boot loader provides a
282 command line at boot time, it is appended to this string to
283 form the full kernel command line, when the system boots.
285 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
286 change this behavior.
288 In most cases, the command line (whether built-in or provided
289 by the boot loader) should specify the device for the root
292 config CMDLINE_OVERRIDE
293 bool "Built-in command line overrides boot loader arguments"
295 depends on CMDLINE_BOOL
297 Set this option to 'Y' to have the kernel ignore the boot loader
298 command line, and use ONLY the built-in command line.
300 This is used to work around broken boot loaders. This should
301 be set to 'N' under normal conditions.
303 config VMALLOC_RESERVE
308 bool "Hardwall support to allow access to user dynamic network"
312 int "Processor protection level for kernel"
316 This setting determines the processor protection level the
317 kernel will be built to run at. Generally you should use
318 the default value here.
320 endmenu # Tilera-specific configuration
328 select GENERIC_PCI_IOMAP
330 Enable PCI root complex support, so PCIe endpoint devices can
331 be attached to the Tile chip. Many, but not all, PCI devices
332 are supported under Tilera's root complex driver.
343 source "drivers/pci/Kconfig"
346 bool "Support for hot-pluggable devices"
348 Say Y here if you want to plug devices into your computer while
349 the system is running, and be able to use them quickly. In many
350 cases, the devices can likewise be unplugged at any time too.
351 One well-known example of this is USB.
353 source "drivers/pci/hotplug/Kconfig"
357 menu "Executable file formats"
364 source "fs/Kconfig.binfmt"
370 source "drivers/Kconfig"
374 source "arch/tile/Kconfig.debug"
376 source "security/Kconfig"
378 source "crypto/Kconfig"
382 source "arch/tile/kvm/Kconfig"