Loading...
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 HAVE_SYSCALL_WRAPPERS if TILEGX
15 select SYS_HYPERVISOR
16 select ARCH_HAVE_NMI_SAFE_CMPXCHG
17 select GENERIC_CLOCKEVENTS
18
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
24# select PERF_EVENTS
25# select HAVE_USER_RETURN_NOTIFIER
26# config NO_BOOTMEM
27# config ARCH_SUPPORTS_DEBUG_PAGEALLOC
28# config HUGETLB_PAGE_SIZE_VARIABLE
29
30config MMU
31 def_bool y
32
33config GENERIC_CSUM
34 def_bool y
35
36config SEMAPHORE_SLEEPERS
37 def_bool y
38
39config HAVE_ARCH_ALLOC_REMAP
40 def_bool y
41
42config HAVE_SETUP_PER_CPU_AREA
43 def_bool y
44
45config NEED_PER_CPU_PAGE_FIRST_CHUNK
46 def_bool y
47
48config SYS_SUPPORTS_HUGETLBFS
49 def_bool y
50
51# Support for additional huge page sizes besides HPAGE_SIZE.
52# The software support is currently only present in the TILE-Gx
53# hypervisor. TILEPro in any case does not support page sizes
54# larger than the default HPAGE_SIZE.
55config HUGETLB_SUPER_PAGES
56 depends on HUGETLB_PAGE && TILEGX
57 def_bool y
58
59# FIXME: tilegx can implement a more efficient rwsem.
60config RWSEM_GENERIC_SPINLOCK
61 def_bool y
62
63# We have a very flat architecture from a migration point of view,
64# so save boot time by presetting this (particularly useful on tile-sim).
65config DEFAULT_MIGRATION_COST
66 int
67 default "10000000"
68
69# We only support gcc 4.4 and above, so this should work.
70config ARCH_SUPPORTS_OPTIMIZED_INLINING
71 def_bool y
72
73config ARCH_PHYS_ADDR_T_64BIT
74 def_bool y
75
76config ARCH_DMA_ADDR_T_64BIT
77 def_bool y
78
79config NEED_DMA_MAP_STATE
80 def_bool y
81
82config LOCKDEP_SUPPORT
83 def_bool y
84
85config STACKTRACE_SUPPORT
86 def_bool y
87 select STACKTRACE
88
89# We use discontigmem for now; at some point we may want to switch
90# to sparsemem (Tilera bug 7996).
91config ARCH_DISCONTIGMEM_ENABLE
92 def_bool y
93
94config ARCH_DISCONTIGMEM_DEFAULT
95 def_bool y
96
97config TRACE_IRQFLAGS_SUPPORT
98 def_bool y
99
100config STRICT_DEVMEM
101 def_bool y
102
103# SMP is required for Tilera Linux.
104config SMP
105 def_bool y
106
107# Allow checking for compile-time determined overflow errors in
108# copy_from_user(). There are still unprovable places in the
109# generic code as of 2.6.34, so this option is not really compatible
110# with -Werror, which is more useful in general.
111config DEBUG_COPY_FROM_USER
112 def_bool n
113
114config HVC_TILE
115 select HVC_DRIVER
116 def_bool y
117
118config TILEGX
119 bool "Building with TILE-Gx (64-bit) compiler and toolchain"
120
121config TILEPRO
122 def_bool !TILEGX
123
124config 64BIT
125 def_bool TILEGX
126
127config ARCH_DEFCONFIG
128 string
129 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
130 default "arch/tile/configs/tilegx_defconfig" if TILEGX
131
132source "init/Kconfig"
133
134menu "Tilera-specific configuration"
135
136config NR_CPUS
137 int "Maximum number of tiles (2-255)"
138 range 2 255
139 depends on SMP
140 default "64"
141 ---help---
142 Building with 64 is the recommended value, but a slightly
143 smaller kernel memory footprint results from using a smaller
144 value on chips with fewer tiles.
145
146if TILEGX
147
148choice
149 prompt "Kernel page size"
150 default PAGE_SIZE_64KB
151 help
152 This lets you select the page size of the kernel. For best
153 performance on memory-intensive applications, a page size of 64KB
154 is recommended. For workloads involving many small files, many
155 connections, etc., it may be better to select 16KB, which uses
156 memory more efficiently at some cost in TLB performance.
157
158 Note that this option is TILE-Gx specific; currently
159 TILEPro page size is set by rebuilding the hypervisor.
160
161config PAGE_SIZE_16KB
162 bool "16KB"
163
164config PAGE_SIZE_64KB
165 bool "64KB"
166
167endchoice
168
169endif
170
171source "kernel/Kconfig.hz"
172
173config KEXEC
174 bool "kexec system call"
175 ---help---
176 kexec is a system call that implements the ability to shutdown your
177 current kernel, and to start another kernel. It is like a reboot
178 but it is independent of the system firmware. It is used
179 to implement the "mboot" Tilera booter.
180
181 The name comes from the similarity to the exec system call.
182
183config COMPAT
184 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
185 depends on TILEGX
186 select COMPAT_BINFMT_ELF
187 default y
188 ---help---
189 If enabled, the kernel will support running TILE-Gx binaries
190 that were built with the -m32 option.
191
192config SYSVIPC_COMPAT
193 def_bool y
194 depends on COMPAT && SYSVIPC
195
196# We do not currently support disabling HIGHMEM on tile64 and tilepro.
197config HIGHMEM
198 bool # "Support for more than 512 MB of RAM"
199 default !TILEGX
200 ---help---
201 Linux can use the full amount of RAM in the system by
202 default. However, the address space of TILE processors is
203 only 4 Gigabytes large. That means that, if you have a large
204 amount of physical memory, not all of it can be "permanently
205 mapped" by the kernel. The physical memory that's not
206 permanently mapped is called "high memory".
207
208 If you are compiling a kernel which will never run on a
209 machine with more than 512 MB total physical RAM, answer
210 "false" here. This will result in the kernel mapping all of
211 physical memory into the top 1 GB of virtual memory space.
212
213 If unsure, say "true".
214
215# We do not currently support disabling NUMA.
216config NUMA
217 bool # "NUMA Memory Allocation and Scheduler Support"
218 depends on SMP && DISCONTIGMEM
219 default y
220 ---help---
221 NUMA memory allocation is required for TILE processors
222 unless booting with memory striping enabled in the
223 hypervisor, or with only a single memory controller.
224 It is recommended that this option always be enabled.
225
226config NODES_SHIFT
227 int "Log base 2 of the max number of memory controllers"
228 default 2
229 depends on NEED_MULTIPLE_NODES
230 ---help---
231 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
232 In a system with more controllers, this value should be raised.
233
234choice
235 depends on !TILEGX
236 prompt "Memory split" if EXPERT
237 default VMSPLIT_3G
238 ---help---
239 Select the desired split between kernel and user memory.
240
241 If the address range available to the kernel is less than the
242 physical memory installed, the remaining memory will be available
243 as "high memory". Accessing high memory is a little more costly
244 than low memory, as it needs to be mapped into the kernel first.
245 Note that increasing the kernel address space limits the range
246 available to user programs, making the address space there
247 tighter. Selecting anything other than the default 3G/1G split
248 will also likely make your kernel incompatible with binary-only
249 kernel modules.
250
251 If you are not absolutely sure what you are doing, leave this
252 option alone!
253
254 config VMSPLIT_3_75G
255 bool "3.75G/0.25G user/kernel split (no kernel networking)"
256 config VMSPLIT_3_5G
257 bool "3.5G/0.5G user/kernel split"
258 config VMSPLIT_3G
259 bool "3G/1G user/kernel split"
260 config VMSPLIT_2_75G
261 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
262 config VMSPLIT_2_5G
263 bool "2.5G/1.5G user/kernel split"
264 config VMSPLIT_2_25G
265 bool "2.25G/1.75G user/kernel split"
266 config VMSPLIT_2G
267 bool "2G/2G user/kernel split"
268 config VMSPLIT_1G
269 bool "1G/3G user/kernel split"
270endchoice
271
272config PAGE_OFFSET
273 hex
274 depends on !64BIT
275 default 0xF0000000 if VMSPLIT_3_75G
276 default 0xE0000000 if VMSPLIT_3_5G
277 default 0xB0000000 if VMSPLIT_2_75G
278 default 0xA0000000 if VMSPLIT_2_5G
279 default 0x90000000 if VMSPLIT_2_25G
280 default 0x80000000 if VMSPLIT_2G
281 default 0x40000000 if VMSPLIT_1G
282 default 0xC0000000
283
284source "mm/Kconfig"
285
286config CMDLINE_BOOL
287 bool "Built-in kernel command line"
288 default n
289 ---help---
290 Allow for specifying boot arguments to the kernel at
291 build time. On some systems (e.g. embedded ones), it is
292 necessary or convenient to provide some or all of the
293 kernel boot arguments with the kernel itself (that is,
294 to not rely on the boot loader to provide them.)
295
296 To compile command line arguments into the kernel,
297 set this option to 'Y', then fill in the
298 the boot arguments in CONFIG_CMDLINE.
299
300 Systems with fully functional boot loaders (e.g. mboot, or
301 if booting over PCI) should leave this option set to 'N'.
302
303config CMDLINE
304 string "Built-in kernel command string"
305 depends on CMDLINE_BOOL
306 default ""
307 ---help---
308 Enter arguments here that should be compiled into the kernel
309 image and used at boot time. If the boot loader provides a
310 command line at boot time, it is appended to this string to
311 form the full kernel command line, when the system boots.
312
313 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
314 change this behavior.
315
316 In most cases, the command line (whether built-in or provided
317 by the boot loader) should specify the device for the root
318 file system.
319
320config CMDLINE_OVERRIDE
321 bool "Built-in command line overrides boot loader arguments"
322 default n
323 depends on CMDLINE_BOOL
324 ---help---
325 Set this option to 'Y' to have the kernel ignore the boot loader
326 command line, and use ONLY the built-in command line.
327
328 This is used to work around broken boot loaders. This should
329 be set to 'N' under normal conditions.
330
331config VMALLOC_RESERVE
332 hex
333 default 0x1000000
334
335config HARDWALL
336 bool "Hardwall support to allow access to user dynamic network"
337 default y
338
339config KERNEL_PL
340 int "Processor protection level for kernel"
341 range 1 2
342 default "1"
343 ---help---
344 This setting determines the processor protection level the
345 kernel will be built to run at. Generally you should use
346 the default value here.
347
348endmenu # Tilera-specific configuration
349
350menu "Bus options"
351
352config PCI
353 bool "PCI support"
354 default y
355 select PCI_DOMAINS
356 select GENERIC_PCI_IOMAP
357 ---help---
358 Enable PCI root complex support, so PCIe endpoint devices can
359 be attached to the Tile chip. Many, but not all, PCI devices
360 are supported under Tilera's root complex driver.
361
362config PCI_DOMAINS
363 bool
364
365config NO_IOMEM
366 def_bool !PCI
367
368config NO_IOPORT
369 def_bool !PCI
370
371source "drivers/pci/Kconfig"
372
373config HOTPLUG
374 bool "Support for hot-pluggable devices"
375 ---help---
376 Say Y here if you want to plug devices into your computer while
377 the system is running, and be able to use them quickly. In many
378 cases, the devices can likewise be unplugged at any time too.
379 One well-known example of this is USB.
380
381source "drivers/pci/hotplug/Kconfig"
382
383endmenu
384
385menu "Executable file formats"
386
387# only elf supported
388config KCORE_ELF
389 def_bool y
390 depends on PROC_FS
391
392source "fs/Kconfig.binfmt"
393
394endmenu
395
396source "net/Kconfig"
397
398source "drivers/Kconfig"
399
400source "fs/Kconfig"
401
402source "arch/tile/Kconfig.debug"
403
404source "security/Kconfig"
405
406source "crypto/Kconfig"
407
408source "lib/Kconfig"
409
410source "arch/tile/kvm/Kconfig"
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_PERF_EVENTS
7 select USE_PMC if PERF_EVENTS
8 select HAVE_DMA_API_DEBUG
9 select HAVE_KVM if !TILEGX
10 select GENERIC_FIND_FIRST_BIT
11 select SYSCTL_EXCEPTION_TRACE
12 select CC_OPTIMIZE_FOR_SIZE
13 select HAVE_DEBUG_KMEMLEAK
14 select GENERIC_IRQ_PROBE
15 select GENERIC_PENDING_IRQ if SMP
16 select GENERIC_IRQ_SHOW
17 select HAVE_DEBUG_BUGVERBOSE
18 select VIRT_TO_BUS
19 select SYS_HYPERVISOR
20 select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
21 select ARCH_HAS_DEVMEM_IS_ALLOWED
22 select ARCH_HAVE_NMI_SAFE_CMPXCHG
23 select GENERIC_CLOCKEVENTS
24 select MODULES_USE_ELF_RELA
25 select HAVE_ARCH_TRACEHOOK
26 select HAVE_SYSCALL_TRACEPOINTS
27 select USER_STACKTRACE_SUPPORT
28 select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
29 select HAVE_DEBUG_STACKOVERFLOW
30 select ARCH_WANT_FRAME_POINTERS
31 select HAVE_CONTEXT_TRACKING
32 select EDAC_SUPPORT
33 select GENERIC_STRNCPY_FROM_USER
34 select GENERIC_STRNLEN_USER
35 select HAVE_ARCH_SECCOMP_FILTER
36
37# FIXME: investigate whether we need/want these options.
38# select HAVE_IOREMAP_PROT
39# select HAVE_OPTPROBES
40# select HAVE_REGS_AND_STACK_ACCESS_API
41# select HAVE_HW_BREAKPOINT
42# select PERF_EVENTS
43# select HAVE_USER_RETURN_NOTIFIER
44# config NO_BOOTMEM
45# config ARCH_SUPPORTS_DEBUG_PAGEALLOC
46# config HUGETLB_PAGE_SIZE_VARIABLE
47
48config MMU
49 def_bool y
50
51config GENERIC_CSUM
52 def_bool y
53
54config HAVE_ARCH_ALLOC_REMAP
55 def_bool y
56
57config HAVE_SETUP_PER_CPU_AREA
58 def_bool y
59
60config NEED_PER_CPU_PAGE_FIRST_CHUNK
61 def_bool y
62
63config SYS_SUPPORTS_HUGETLBFS
64 def_bool y
65
66# Support for additional huge page sizes besides HPAGE_SIZE.
67# The software support is currently only present in the TILE-Gx
68# hypervisor. TILEPro in any case does not support page sizes
69# larger than the default HPAGE_SIZE.
70config HUGETLB_SUPER_PAGES
71 depends on HUGETLB_PAGE && TILEGX
72 def_bool y
73
74config GENERIC_TIME_VSYSCALL
75 def_bool y
76
77# Enable PMC if PERF_EVENTS, OPROFILE, or WATCHPOINTS are enabled.
78config USE_PMC
79 bool
80
81# FIXME: tilegx can implement a more efficient rwsem.
82config RWSEM_GENERIC_SPINLOCK
83 def_bool y
84
85# We only support gcc 4.4 and above, so this should work.
86config ARCH_SUPPORTS_OPTIMIZED_INLINING
87 def_bool y
88
89config ARCH_PHYS_ADDR_T_64BIT
90 def_bool y
91
92config ARCH_DMA_ADDR_T_64BIT
93 def_bool y
94
95config NEED_DMA_MAP_STATE
96 def_bool y
97
98config ARCH_HAS_DMA_SET_COHERENT_MASK
99 bool
100
101config LOCKDEP_SUPPORT
102 def_bool y
103
104config STACKTRACE_SUPPORT
105 def_bool y
106 select STACKTRACE
107
108# We use discontigmem for now; at some point we may want to switch
109# to sparsemem (Tilera bug 7996).
110config ARCH_DISCONTIGMEM_ENABLE
111 def_bool y
112
113config ARCH_DISCONTIGMEM_DEFAULT
114 def_bool y
115
116config TRACE_IRQFLAGS_SUPPORT
117 def_bool y
118
119# SMP is required for Tilera Linux.
120config SMP
121 def_bool y
122
123config HVC_TILE
124 depends on TTY
125 select HVC_DRIVER
126 select HVC_IRQ if TILEGX
127 def_bool y
128
129# Building with ARCH=tilegx (or ARCH=tile) implies using the
130# 64-bit TILE-Gx toolchain, so force CONFIG_TILEGX on.
131config TILEGX
132 def_bool ARCH != "tilepro"
133 select SPARSE_IRQ
134 select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
135 select HAVE_FUNCTION_TRACER
136 select HAVE_FUNCTION_GRAPH_TRACER
137 select HAVE_DYNAMIC_FTRACE
138 select HAVE_FTRACE_MCOUNT_RECORD
139 select HAVE_KPROBES
140 select HAVE_KRETPROBES
141 select HAVE_ARCH_KGDB
142 select ARCH_SUPPORTS_ATOMIC_RMW
143 select HAVE_ARCH_JUMP_LABEL
144
145config TILEPRO
146 def_bool !TILEGX
147
148config 64BIT
149 def_bool TILEGX
150
151config ARCH_DEFCONFIG
152 string
153 default "arch/tile/configs/tilepro_defconfig" if !TILEGX
154 default "arch/tile/configs/tilegx_defconfig" if TILEGX
155
156config PGTABLE_LEVELS
157 int
158 default 3 if 64BIT
159 default 2
160
161source "init/Kconfig"
162
163source "kernel/Kconfig.freezer"
164
165menu "Tilera-specific configuration"
166
167config NR_CPUS
168 int "Maximum number of tiles (2-255)"
169 range 2 255
170 depends on SMP
171 default "64"
172 ---help---
173 Building with 64 is the recommended value, but a slightly
174 smaller kernel memory footprint results from using a smaller
175 value on chips with fewer tiles.
176
177choice
178 prompt "Kernel page size"
179 default PAGE_SIZE_64KB
180 help
181 This lets you select the page size of the kernel. For best
182 performance on memory-intensive applications, a page size of 64KB
183 is recommended. For workloads involving many small files, many
184 connections, etc., it may be better to select 16KB, which uses
185 memory more efficiently at some cost in TLB performance.
186
187 Note that for TILEPro, you must also rebuild the hypervisor
188 with a matching page size.
189
190config PAGE_SIZE_4KB
191 bool "4KB" if TILEPRO
192
193config PAGE_SIZE_16KB
194 bool "16KB"
195
196config PAGE_SIZE_64KB
197 bool "64KB"
198
199endchoice
200
201source "kernel/Kconfig.hz"
202
203config KEXEC
204 bool "kexec system call"
205 select KEXEC_CORE
206 ---help---
207 kexec is a system call that implements the ability to shutdown your
208 current kernel, and to start another kernel. It is like a reboot
209 but it is independent of the system firmware. It is used
210 to implement the "mboot" Tilera booter.
211
212 The name comes from the similarity to the exec system call.
213
214config COMPAT
215 bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
216 depends on TILEGX
217 select COMPAT_BINFMT_ELF
218 default y
219 ---help---
220 If enabled, the kernel will support running TILE-Gx binaries
221 that were built with the -m32 option.
222
223config SECCOMP
224 bool "Enable seccomp to safely compute untrusted bytecode"
225 depends on PROC_FS
226 help
227 This kernel feature is useful for number crunching applications
228 that may need to compute untrusted bytecode during their
229 execution. By using pipes or other transports made available to
230 the process as file descriptors supporting the read/write
231 syscalls, it's possible to isolate those applications in
232 their own address space using seccomp. Once seccomp is
233 enabled via prctl, it cannot be disabled and the task is only
234 allowed to execute a few safe syscalls defined by each seccomp
235 mode.
236
237 If unsure, say N.
238
239config SYSVIPC_COMPAT
240 def_bool y
241 depends on COMPAT && SYSVIPC
242
243# We do not currently support disabling HIGHMEM on tilepro.
244config HIGHMEM
245 bool # "Support for more than 512 MB of RAM"
246 default !TILEGX
247 ---help---
248 Linux can use the full amount of RAM in the system by
249 default. However, the address space of TILE processors is
250 only 4 Gigabytes large. That means that, if you have a large
251 amount of physical memory, not all of it can be "permanently
252 mapped" by the kernel. The physical memory that's not
253 permanently mapped is called "high memory".
254
255 If you are compiling a kernel which will never run on a
256 machine with more than 512 MB total physical RAM, answer
257 "false" here. This will result in the kernel mapping all of
258 physical memory into the top 1 GB of virtual memory space.
259
260 If unsure, say "true".
261
262config ZONE_DMA
263 def_bool y
264
265config IOMMU_HELPER
266 bool
267
268config NEED_SG_DMA_LENGTH
269 bool
270
271config SWIOTLB
272 bool
273 default TILEGX
274 select IOMMU_HELPER
275 select NEED_SG_DMA_LENGTH
276 select ARCH_HAS_DMA_SET_COHERENT_MASK
277
278# We do not currently support disabling NUMA.
279config NUMA
280 bool # "NUMA Memory Allocation and Scheduler Support"
281 depends on SMP && DISCONTIGMEM
282 default y
283 ---help---
284 NUMA memory allocation is required for TILE processors
285 unless booting with memory striping enabled in the
286 hypervisor, or with only a single memory controller.
287 It is recommended that this option always be enabled.
288
289config NODES_SHIFT
290 int "Log base 2 of the max number of memory controllers"
291 default 2
292 depends on NEED_MULTIPLE_NODES
293 ---help---
294 By default, 2, i.e. 2^2 == 4 DDR2 controllers.
295 In a system with more controllers, this value should be raised.
296
297choice
298 depends on !TILEGX
299 prompt "Memory split" if EXPERT
300 default VMSPLIT_3G
301 ---help---
302 Select the desired split between kernel and user memory.
303
304 If the address range available to the kernel is less than the
305 physical memory installed, the remaining memory will be available
306 as "high memory". Accessing high memory is a little more costly
307 than low memory, as it needs to be mapped into the kernel first.
308 Note that increasing the kernel address space limits the range
309 available to user programs, making the address space there
310 tighter. Selecting anything other than the default 3G/1G split
311 will also likely make your kernel incompatible with binary-only
312 kernel modules.
313
314 If you are not absolutely sure what you are doing, leave this
315 option alone!
316
317 config VMSPLIT_3_75G
318 bool "3.75G/0.25G user/kernel split (no kernel networking)"
319 config VMSPLIT_3_5G
320 bool "3.5G/0.5G user/kernel split"
321 config VMSPLIT_3G
322 bool "3G/1G user/kernel split"
323 config VMSPLIT_2_75G
324 bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
325 config VMSPLIT_2_5G
326 bool "2.5G/1.5G user/kernel split"
327 config VMSPLIT_2_25G
328 bool "2.25G/1.75G user/kernel split"
329 config VMSPLIT_2G
330 bool "2G/2G user/kernel split"
331 config VMSPLIT_1G
332 bool "1G/3G user/kernel split"
333endchoice
334
335config PAGE_OFFSET
336 hex
337 depends on !64BIT
338 default 0xF0000000 if VMSPLIT_3_75G
339 default 0xE0000000 if VMSPLIT_3_5G
340 default 0xB0000000 if VMSPLIT_2_75G
341 default 0xA0000000 if VMSPLIT_2_5G
342 default 0x90000000 if VMSPLIT_2_25G
343 default 0x80000000 if VMSPLIT_2G
344 default 0x40000000 if VMSPLIT_1G
345 default 0xC0000000
346
347source "mm/Kconfig"
348
349source "kernel/Kconfig.preempt"
350
351config CMDLINE_BOOL
352 bool "Built-in kernel command line"
353 default n
354 ---help---
355 Allow for specifying boot arguments to the kernel at
356 build time. On some systems (e.g. embedded ones), it is
357 necessary or convenient to provide some or all of the
358 kernel boot arguments with the kernel itself (that is,
359 to not rely on the boot loader to provide them.)
360
361 To compile command line arguments into the kernel,
362 set this option to 'Y', then fill in the
363 the boot arguments in CONFIG_CMDLINE.
364
365 Systems with fully functional boot loaders (e.g. mboot, or
366 if booting over PCI) should leave this option set to 'N'.
367
368config CMDLINE
369 string "Built-in kernel command string"
370 depends on CMDLINE_BOOL
371 default ""
372 ---help---
373 Enter arguments here that should be compiled into the kernel
374 image and used at boot time. If the boot loader provides a
375 command line at boot time, it is appended to this string to
376 form the full kernel command line, when the system boots.
377
378 However, you can use the CONFIG_CMDLINE_OVERRIDE option to
379 change this behavior.
380
381 In most cases, the command line (whether built-in or provided
382 by the boot loader) should specify the device for the root
383 file system.
384
385config CMDLINE_OVERRIDE
386 bool "Built-in command line overrides boot loader arguments"
387 default n
388 depends on CMDLINE_BOOL
389 ---help---
390 Set this option to 'Y' to have the kernel ignore the boot loader
391 command line, and use ONLY the built-in command line.
392
393 This is used to work around broken boot loaders. This should
394 be set to 'N' under normal conditions.
395
396config VMALLOC_RESERVE
397 hex
398 default 0x2000000
399
400config HARDWALL
401 bool "Hardwall support to allow access to user dynamic network"
402 default y
403
404config KERNEL_PL
405 int "Processor protection level for kernel"
406 range 1 2
407 default 2 if TILEGX
408 default 1 if !TILEGX
409 ---help---
410 Since MDE 4.2, the Tilera hypervisor runs the kernel
411 at PL2 by default. If running under an older hypervisor,
412 or as a KVM guest, you must run at PL1. (The current
413 hypervisor may also be recompiled with "make HV_PL=2" to
414 allow it to run a kernel at PL1, but clients running at PL1
415 are not expected to be supported indefinitely.)
416
417 If you're not sure, don't change the default.
418
419source "arch/tile/gxio/Kconfig"
420
421endmenu # Tilera-specific configuration
422
423menu "Bus options"
424
425config PCI
426 bool "PCI support"
427 default y
428 select PCI_DOMAINS
429 select GENERIC_PCI_IOMAP
430 select TILE_GXIO_TRIO if TILEGX
431 select PCI_MSI if TILEGX
432 ---help---
433 Enable PCI root complex support, so PCIe endpoint devices can
434 be attached to the Tile chip. Many, but not all, PCI devices
435 are supported under Tilera's root complex driver.
436
437config PCI_DOMAINS
438 bool
439
440config NO_IOMEM
441 def_bool !PCI
442
443config NO_IOPORT_MAP
444 def_bool !PCI
445
446config TILE_PCI_IO
447 bool "PCI I/O space support"
448 default n
449 depends on PCI
450 depends on TILEGX
451 ---help---
452 Enable PCI I/O space support on TILEGx. Since the PCI I/O space
453 is used by few modern PCIe endpoint devices, its support is disabled
454 by default to save the TRIO PIO Region resource for other purposes.
455
456source "drivers/pci/Kconfig"
457
458config TILE_USB
459 tristate "Tilera USB host adapter support"
460 default y
461 depends on USB
462 depends on TILEGX
463 select TILE_GXIO_USB_HOST
464 ---help---
465 Provides USB host adapter support for the built-in EHCI and OHCI
466 interfaces on TILE-Gx chips.
467
468endmenu
469
470menu "Executable file formats"
471
472source "fs/Kconfig.binfmt"
473
474endmenu
475
476source "net/Kconfig"
477
478source "drivers/Kconfig"
479
480source "fs/Kconfig"
481
482source "arch/tile/Kconfig.debug"
483
484source "security/Kconfig"
485
486source "crypto/Kconfig"
487
488source "lib/Kconfig"
489
490source "arch/tile/kvm/Kconfig"