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 ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
11 select HAVE_GENERIC_HARDIRQS
12 select GENERIC_IRQ_PROBE
13 select GENERIC_PENDING_IRQ if SMP
14 select GENERIC_IRQ_SHOW
16 select ARCH_HAVE_NMI_SAFE_CMPXCHG if !M386
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
53 config GENERIC_CLOCKEVENTS
56 # FIXME: tilegx can implement a more efficient rwsem.
57 config RWSEM_GENERIC_SPINLOCK
60 # We have a very flat architecture from a migration point of view,
61 # so save boot time by presetting this (particularly useful on tile-sim).
62 config DEFAULT_MIGRATION_COST
66 # We only support gcc 4.4 and above, so this should work.
67 config ARCH_SUPPORTS_OPTIMIZED_INLINING
70 config ARCH_PHYS_ADDR_T_64BIT
73 config ARCH_DMA_ADDR_T_64BIT
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.
105 # Please note: TILE-Gx support is not yet finalized; this is
106 # the preliminary support. TILE-Gx drivers are only provided
107 # with the alpha or beta test versions for Tilera customers.
109 depends on EXPERIMENTAL
110 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
116 config ARCH_DEFCONFIG
118 default "arch/tile/configs/tile_defconfig" if !TILEGX
119 default "arch/tile/configs/tilegx_defconfig" if TILEGX
121 source "init/Kconfig"
123 menu "Tilera-specific configuration"
126 int "Maximum number of tiles (2-255)"
131 Building with 64 is the recommended value, but a slightly
132 smaller kernel memory footprint results from using a smaller
133 value on chips with fewer tiles.
135 source "kernel/time/Kconfig"
137 source "kernel/Kconfig.hz"
140 bool "kexec system call"
142 kexec is a system call that implements the ability to shutdown your
143 current kernel, and to start another kernel. It is like a reboot
144 but it is independent of the system firmware. It is used
145 to implement the "mboot" Tilera booter.
147 The name comes from the similarity to the exec system call.
150 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
152 select COMPAT_BINFMT_ELF
155 If enabled, the kernel will support running TILE-Gx binaries
156 that were built with the -m32 option.
158 config SYSVIPC_COMPAT
160 depends on COMPAT && SYSVIPC
162 # We do not currently support disabling HIGHMEM on tile64 and tilepro.
164 bool # "Support for more than 512 MB of RAM"
167 Linux can use the full amount of RAM in the system by
168 default. However, the address space of TILE processors is
169 only 4 Gigabytes large. That means that, if you have a large
170 amount of physical memory, not all of it can be "permanently
171 mapped" by the kernel. The physical memory that's not
172 permanently mapped is called "high memory".
174 If you are compiling a kernel which will never run on a
175 machine with more than 512 MB total physical RAM, answer
176 "false" here. This will result in the kernel mapping all of
177 physical memory into the top 1 GB of virtual memory space.
179 If unsure, say "true".
181 # We do not currently support disabling NUMA.
183 bool # "NUMA Memory Allocation and Scheduler Support"
184 depends on SMP && DISCONTIGMEM
187 NUMA memory allocation is required for TILE processors
188 unless booting with memory striping enabled in the
189 hypervisor, or with only a single memory controller.
190 It is recommended that this option always be enabled.
193 int "Log base 2 of the max number of memory controllers"
195 depends on NEED_MULTIPLE_NODES
197 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
198 In a system with more controllers, this value should be raised.
202 prompt "Memory split" if EXPERT
205 Select the desired split between kernel and user memory.
207 If the address range available to the kernel is less than the
208 physical memory installed, the remaining memory will be available
209 as "high memory". Accessing high memory is a little more costly
210 than low memory, as it needs to be mapped into the kernel first.
211 Note that increasing the kernel address space limits the range
212 available to user programs, making the address space there
213 tighter. Selecting anything other than the default 3G/1G split
214 will also likely make your kernel incompatible with binary-only
217 If you are not absolutely sure what you are doing, leave this
221 bool "3.75G/0.25G user/kernel split (no kernel networking)"
223 bool "3.5G/0.5G user/kernel split"
225 bool "3G/1G user/kernel split"
227 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
229 bool "2.5G/1.5G user/kernel split"
231 bool "2.25G/1.75G user/kernel split"
233 bool "2G/2G user/kernel split"
235 bool "1G/3G user/kernel split"
240 default 0xF0000000 if VMSPLIT_3_75G
241 default 0xE0000000 if VMSPLIT_3_5G
242 default 0xB0000000 if VMSPLIT_2_75G
243 default 0xA0000000 if VMSPLIT_2_5G
244 default 0x90000000 if VMSPLIT_2_25G
245 default 0x80000000 if VMSPLIT_2G
246 default 0x40000000 if VMSPLIT_1G
252 bool "Built-in kernel command line"
255 Allow for specifying boot arguments to the kernel at
256 build time. On some systems (e.g. embedded ones), it is
257 necessary or convenient to provide some or all of the
258 kernel boot arguments with the kernel itself (that is,
259 to not rely on the boot loader to provide them.)
261 To compile command line arguments into the kernel,
262 set this option to 'Y', then fill in the
263 the boot arguments in CONFIG_CMDLINE.
265 Systems with fully functional boot loaders (e.g. mboot, or
266 if booting over PCI) should leave this option set to 'N'.
269 string "Built-in kernel command string"
270 depends on CMDLINE_BOOL
273 Enter arguments here that should be compiled into the kernel
274 image and used at boot time. If the boot loader provides a
275 command line at boot time, it is appended to this string to
276 form the full kernel command line, when the system boots.
278 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
279 change this behavior.
281 In most cases, the command line (whether built-in or provided
282 by the boot loader) should specify the device for the root
285 config CMDLINE_OVERRIDE
286 bool "Built-in command line overrides boot loader arguments"
288 depends on CMDLINE_BOOL
290 Set this option to 'Y' to have the kernel ignore the boot loader
291 command line, and use ONLY the built-in command line.
293 This is used to work around broken boot loaders. This should
294 be set to 'N' under normal conditions.
296 config VMALLOC_RESERVE
301 bool "Hardwall support to allow access to user dynamic network"
305 int "Processor protection level for kernel"
309 This setting determines the processor protection level the
310 kernel will be built to run at. Generally you should use
311 the default value here.
313 endmenu # Tilera-specific configuration
322 Enable PCI root complex support, so PCIe endpoint devices can
323 be attached to the Tile chip. Many, but not all, PCI devices
324 are supported under Tilera's root complex driver.
335 source "drivers/pci/Kconfig"
338 bool "Support for hot-pluggable devices"
340 Say Y here if you want to plug devices into your computer while
341 the system is running, and be able to use them quickly. In many
342 cases, the devices can likewise be unplugged at any time too.
343 One well-known example of this is USB.
345 source "drivers/pci/hotplug/Kconfig"
349 menu "Executable file formats"
356 source "fs/Kconfig.binfmt"
362 source "drivers/Kconfig"
366 source "arch/tile/Kconfig.debug"
368 source "security/Kconfig"
370 source "crypto/Kconfig"
374 source "arch/tile/kvm/Kconfig"