tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1# For a description of the syntax of this configuration file,
2# see Documentation/kbuild/kconfig-language.txt.
3
4config TILE
5 def_bool y
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 SYS_HYPERVISOR
15 select ARCH_HAVE_NMI_SAFE_CMPXCHG if !M386
16
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
22# select PERF_EVENTS
23# select HAVE_USER_RETURN_NOTIFIER
24# config NO_BOOTMEM
25# config ARCH_SUPPORTS_DEBUG_PAGEALLOC
26# config HUGETLB_PAGE_SIZE_VARIABLE
27
28config MMU
29 def_bool y
30
31config GENERIC_CSUM
32 def_bool y
33
34config SEMAPHORE_SLEEPERS
35 def_bool y
36
37config HAVE_ARCH_ALLOC_REMAP
38 def_bool y
39
40config HAVE_SETUP_PER_CPU_AREA
41 def_bool y
42
43config NEED_PER_CPU_PAGE_FIRST_CHUNK
44 def_bool y
45
46config SYS_SUPPORTS_HUGETLBFS
47 def_bool y
48
49config GENERIC_TIME
50 def_bool y
51
52config GENERIC_CLOCKEVENTS
53 def_bool y
54
55# FIXME: tilegx can implement a more efficient rwsem.
56config RWSEM_GENERIC_SPINLOCK
57 def_bool y
58
59# We have a very flat architecture from a migration point of view,
60# so save boot time by presetting this (particularly useful on tile-sim).
61config DEFAULT_MIGRATION_COST
62 int
63 default "10000000"
64
65# We only support gcc 4.4 and above, so this should work.
66config ARCH_SUPPORTS_OPTIMIZED_INLINING
67 def_bool y
68
69config ARCH_PHYS_ADDR_T_64BIT
70 def_bool y
71
72config ARCH_DMA_ADDR_T_64BIT
73 def_bool y
74
75config LOCKDEP_SUPPORT
76 def_bool y
77
78config STACKTRACE_SUPPORT
79 def_bool y
80 select STACKTRACE
81
82# We use discontigmem for now; at some point we may want to switch
83# to sparsemem (Tilera bug 7996).
84config ARCH_DISCONTIGMEM_ENABLE
85 def_bool y
86
87config ARCH_DISCONTIGMEM_DEFAULT
88 def_bool y
89
90config TRACE_IRQFLAGS_SUPPORT
91 def_bool y
92
93config STRICT_DEVMEM
94 def_bool y
95
96# SMP is required for Tilera Linux.
97config SMP
98 def_bool y
99
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.
104config DEBUG_COPY_FROM_USER
105 def_bool n
106
107config HVC_TILE
108 select HVC_DRIVER
109 def_bool y
110
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.
114config TILEGX
115 depends on EXPERIMENTAL
116 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
117
118config 64BIT
119 depends on TILEGX
120 def_bool y
121
122config ARCH_DEFCONFIG
123 string
124 default "arch/tile/configs/tile_defconfig" if !TILEGX
125 default "arch/tile/configs/tilegx_defconfig" if TILEGX
126
127source "init/Kconfig"
128
129menu "Tilera-specific configuration"
130
131config NR_CPUS
132 int "Maximum number of tiles (2-255)"
133 range 2 255
134 depends on SMP
135 default "64"
136 ---help---
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.
140
141source "kernel/time/Kconfig"
142
143source "kernel/Kconfig.hz"
144
145config KEXEC
146 bool "kexec system call"
147 ---help---
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.
152
153 The name comes from the similarity to the exec system call.
154
155config COMPAT
156 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
157 depends on TILEGX
158 select COMPAT_BINFMT_ELF
159 default y
160 ---help---
161 If enabled, the kernel will support running TILE-Gx binaries
162 that were built with the -m32 option.
163
164config SYSVIPC_COMPAT
165 def_bool y
166 depends on COMPAT && SYSVIPC
167
168# We do not currently support disabling HIGHMEM on tile64 and tilepro.
169config HIGHMEM
170 bool # "Support for more than 512 MB of RAM"
171 default !TILEGX
172 ---help---
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".
179
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.
184
185 If unsure, say "true".
186
187# We do not currently support disabling NUMA.
188config NUMA
189 bool # "NUMA Memory Allocation and Scheduler Support"
190 depends on SMP && DISCONTIGMEM
191 default y
192 ---help---
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.
197
198config NODES_SHIFT
199 int "Log base 2 of the max number of memory controllers"
200 default 2
201 depends on NEED_MULTIPLE_NODES
202 ---help---
203 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
204 In a system with more controllers, this value should be raised.
205
206choice
207 depends on !TILEGX
208 prompt "Memory split" if EXPERT
209 default VMSPLIT_3G
210 ---help---
211 Select the desired split between kernel and user memory.
212
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
221 kernel modules.
222
223 If you are not absolutely sure what you are doing, leave this
224 option alone!
225
226 config VMSPLIT_3_75G
227 bool "3.75G/0.25G user/kernel split (no kernel networking)"
228 config VMSPLIT_3_5G
229 bool "3.5G/0.5G user/kernel split"
230 config VMSPLIT_3G
231 bool "3G/1G user/kernel split"
232 config VMSPLIT_2_75G
233 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
234 config VMSPLIT_2_5G
235 bool "2.5G/1.5G user/kernel split"
236 config VMSPLIT_2_25G
237 bool "2.25G/1.75G user/kernel split"
238 config VMSPLIT_2G
239 bool "2G/2G user/kernel split"
240 config VMSPLIT_1G
241 bool "1G/3G user/kernel split"
242endchoice
243
244config PAGE_OFFSET
245 hex
246 default 0xF0000000 if VMSPLIT_3_75G
247 default 0xE0000000 if VMSPLIT_3_5G
248 default 0xB0000000 if VMSPLIT_2_75G
249 default 0xA0000000 if VMSPLIT_2_5G
250 default 0x90000000 if VMSPLIT_2_25G
251 default 0x80000000 if VMSPLIT_2G
252 default 0x40000000 if VMSPLIT_1G
253 default 0xC0000000
254
255source "mm/Kconfig"
256
257config CMDLINE_BOOL
258 bool "Built-in kernel command line"
259 default n
260 ---help---
261 Allow for specifying boot arguments to the kernel at
262 build time. On some systems (e.g. embedded ones), it is
263 necessary or convenient to provide some or all of the
264 kernel boot arguments with the kernel itself (that is,
265 to not rely on the boot loader to provide them.)
266
267 To compile command line arguments into the kernel,
268 set this option to 'Y', then fill in the
269 the boot arguments in CONFIG_CMDLINE.
270
271 Systems with fully functional boot loaders (e.g. mboot, or
272 if booting over PCI) should leave this option set to 'N'.
273
274config CMDLINE
275 string "Built-in kernel command string"
276 depends on CMDLINE_BOOL
277 default ""
278 ---help---
279 Enter arguments here that should be compiled into the kernel
280 image and used at boot time. If the boot loader provides a
281 command line at boot time, it is appended to this string to
282 form the full kernel command line, when the system boots.
283
284 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
285 change this behavior.
286
287 In most cases, the command line (whether built-in or provided
288 by the boot loader) should specify the device for the root
289 file system.
290
291config CMDLINE_OVERRIDE
292 bool "Built-in command line overrides boot loader arguments"
293 default n
294 depends on CMDLINE_BOOL
295 ---help---
296 Set this option to 'Y' to have the kernel ignore the boot loader
297 command line, and use ONLY the built-in command line.
298
299 This is used to work around broken boot loaders. This should
300 be set to 'N' under normal conditions.
301
302config VMALLOC_RESERVE
303 hex
304 default 0x1000000
305
306config HARDWALL
307 bool "Hardwall support to allow access to user dynamic network"
308 default y
309
310config KERNEL_PL
311 int "Processor protection level for kernel"
312 range 1 2
313 default "1"
314 ---help---
315 This setting determines the processor protection level the
316 kernel will be built to run at. Generally you should use
317 the default value here.
318
319endmenu # Tilera-specific configuration
320
321menu "Bus options"
322
323config PCI
324 bool "PCI support"
325 default y
326 select PCI_DOMAINS
327 ---help---
328 Enable PCI root complex support, so PCIe endpoint devices can
329 be attached to the Tile chip. Many, but not all, PCI devices
330 are supported under Tilera's root complex driver.
331
332config PCI_DOMAINS
333 bool
334
335config NO_IOMEM
336 def_bool !PCI
337
338config NO_IOPORT
339 def_bool !PCI
340
341source "drivers/pci/Kconfig"
342
343config HOTPLUG
344 bool "Support for hot-pluggable devices"
345 ---help---
346 Say Y here if you want to plug devices into your computer while
347 the system is running, and be able to use them quickly. In many
348 cases, the devices can likewise be unplugged at any time too.
349 One well-known example of this is USB.
350
351source "drivers/pci/hotplug/Kconfig"
352
353endmenu
354
355menu "Executable file formats"
356
357# only elf supported
358config KCORE_ELF
359 def_bool y
360 depends on PROC_FS
361
362source "fs/Kconfig.binfmt"
363
364endmenu
365
366source "net/Kconfig"
367
368source "drivers/Kconfig"
369
370source "fs/Kconfig"
371
372source "arch/tile/Kconfig.debug"
373
374source "security/Kconfig"
375
376source "crypto/Kconfig"
377
378source "lib/Kconfig"
379
380source "arch/tile/kvm/Kconfig"