Kconfig 12.3 KB
Newer Older
1
# SPDX-License-Identifier: GPL-2.0
2
# For a description of the syntax of this configuration file,
3
# see Documentation/kbuild/kconfig-language.txt.
4

5
config TILE
6
	def_bool y
7
	select ARCH_HAS_DEVMEM_IS_ALLOWED
8
	select ARCH_HAVE_NMI_SAFE_CMPXCHG
Chris Metcalf's avatar
Chris Metcalf committed
9
	select ARCH_WANT_FRAME_POINTERS
10
	select CC_OPTIMIZE_FOR_SIZE
11
	select EDAC_SUPPORT
12 13 14 15 16
	select GENERIC_CLOCKEVENTS
	select GENERIC_FIND_FIRST_BIT
	select GENERIC_IRQ_PROBE
	select GENERIC_IRQ_SHOW
	select GENERIC_PENDING_IRQ if SMP
17 18
	select GENERIC_STRNCPY_FROM_USER
	select GENERIC_STRNLEN_USER
19
	select HAVE_ARCH_SECCOMP_FILTER
20 21 22 23 24 25
	select HAVE_ARCH_TRACEHOOK
	select HAVE_CONTEXT_TRACKING
	select HAVE_DEBUG_BUGVERBOSE
	select HAVE_DEBUG_KMEMLEAK
	select HAVE_DEBUG_STACKOVERFLOW
	select HAVE_DMA_API_DEBUG
26
	select HAVE_EXIT_THREAD
27
	select HAVE_KVM if !TILEGX
28
	select HAVE_NMI if USE_PMC
29 30 31 32 33 34 35 36
	select HAVE_PERF_EVENTS
	select HAVE_SYSCALL_TRACEPOINTS
	select MODULES_USE_ELF_RELA
	select SYSCTL_EXCEPTION_TRACE
	select SYS_HYPERVISOR
	select USER_STACKTRACE_SUPPORT
	select USE_PMC if PERF_EVENTS
	select VIRT_TO_BUS
37

38
config MMU
39 40
	def_bool y

41
config GENERIC_CSUM
42 43 44 45 46 47 48 49 50
	def_bool y

config HAVE_ARCH_ALLOC_REMAP
	def_bool y

config HAVE_SETUP_PER_CPU_AREA
	def_bool y

config NEED_PER_CPU_PAGE_FIRST_CHUNK
51
	def_bool y
52 53 54 55

config SYS_SUPPORTS_HUGETLBFS
	def_bool y

56 57 58 59 60 61 62 63
# Support for additional huge page sizes besides HPAGE_SIZE.
# The software support is currently only present in the TILE-Gx
# hypervisor. TILEPro in any case does not support page sizes
# larger than the default HPAGE_SIZE.
config HUGETLB_SUPER_PAGES
	depends on HUGETLB_PAGE && TILEGX
	def_bool y

64 65 66
config GENERIC_TIME_VSYSCALL
	def_bool y

67 68 69 70
# Enable PMC if PERF_EVENTS, OPROFILE, or WATCHPOINTS are enabled.
config USE_PMC
	bool

Lucas De Marchi's avatar
Lucas De Marchi committed
71
# FIXME: tilegx can implement a more efficient rwsem.
72 73 74 75 76 77 78 79 80 81
config RWSEM_GENERIC_SPINLOCK
	def_bool y

# We only support gcc 4.4 and above, so this should work.
config ARCH_SUPPORTS_OPTIMIZED_INLINING
	def_bool y

config ARCH_PHYS_ADDR_T_64BIT
	def_bool y

82 83 84
config ARCH_DMA_ADDR_T_64BIT
	def_bool y

85 86 87
config NEED_DMA_MAP_STATE
	def_bool y

88 89 90
config ARCH_HAS_DMA_SET_COHERENT_MASK
	bool

91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113
config LOCKDEP_SUPPORT
	def_bool y

config STACKTRACE_SUPPORT
	def_bool y
	select STACKTRACE

# We use discontigmem for now; at some point we may want to switch
# to sparsemem (Tilera bug 7996).
config ARCH_DISCONTIGMEM_ENABLE
	def_bool y

config ARCH_DISCONTIGMEM_DEFAULT
	def_bool y

config TRACE_IRQFLAGS_SUPPORT
	def_bool y

# SMP is required for Tilera Linux.
config SMP
	def_bool y

config HVC_TILE
114
	depends on TTY
115
	select HVC_DRIVER
116
	select HVC_IRQ if TILEGX
117 118
	def_bool y

119 120
# Building with ARCH=tilegx (or ARCH=tile) implies using the
# 64-bit TILE-Gx toolchain, so force CONFIG_TILEGX on.
121
config TILEGX
122
	def_bool ARCH != "tilepro"
123
	select ARCH_SUPPORTS_ATOMIC_RMW
Thomas Gleixner's avatar
Thomas Gleixner committed
124
	select GENERIC_IRQ_LEGACY_ALLOC_HWIRQ
125 126
	select HAVE_ARCH_JUMP_LABEL
	select HAVE_ARCH_KGDB
Tony Lu's avatar
Tony Lu committed
127 128
	select HAVE_DYNAMIC_FTRACE
	select HAVE_FTRACE_MCOUNT_RECORD
129 130
	select HAVE_FUNCTION_GRAPH_TRACER
	select HAVE_FUNCTION_TRACER
Tony Lu's avatar
Tony Lu committed
131 132
	select HAVE_KPROBES
	select HAVE_KRETPROBES
133
	select SPARSE_IRQ
134

135 136 137
config TILEPRO
	def_bool !TILEGX

138
config 64BIT
139
	def_bool TILEGX
140 141 142

config ARCH_DEFCONFIG
	string
143
	default "arch/tile/configs/tilepro_defconfig" if !TILEGX
144 145
	default "arch/tile/configs/tilegx_defconfig" if TILEGX

146 147 148 149 150
config PGTABLE_LEVELS
	int
	default 3 if 64BIT
	default 2

151 152
source "init/Kconfig"

153 154
source "kernel/Kconfig.freezer"

155 156 157 158 159 160 161 162 163 164 165 166
menu "Tilera-specific configuration"

config NR_CPUS
	int "Maximum number of tiles (2-255)"
	range 2 255
	depends on SMP
	default "64"
	---help---
	  Building with 64 is the recommended value, but a slightly
	  smaller kernel memory footprint results from using a smaller
	  value on chips with fewer tiles.

167 168 169 170 171 172 173 174 175 176
choice
	prompt "Kernel page size"
	default PAGE_SIZE_64KB
	help
	  This lets you select the page size of the kernel.  For best
	  performance on memory-intensive applications, a page size of 64KB
	  is recommended.  For workloads involving many small files, many
	  connections, etc., it may be better to select 16KB, which uses
	  memory more efficiently at some cost in TLB performance.

177 178 179 180 181
	  Note that for TILEPro, you must also rebuild the hypervisor
	  with a matching page size.

config PAGE_SIZE_4KB
	bool "4KB" if TILEPRO
182 183 184 185 186 187 188 189 190

config PAGE_SIZE_16KB
	bool "16KB"

config PAGE_SIZE_64KB
	bool "64KB"

endchoice

191 192 193 194
source "kernel/Kconfig.hz"

config KEXEC
	bool "kexec system call"
195
	select KEXEC_CORE
196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212
	---help---
	  kexec is a system call that implements the ability to shutdown your
	  current kernel, and to start another kernel.  It is like a reboot
	  but it is independent of the system firmware.   It is used
	  to implement the "mboot" Tilera booter.

	  The name comes from the similarity to the exec system call.

config COMPAT
	bool "Support 32-bit TILE-Gx binaries in addition to 64-bit"
	depends on TILEGX
	select COMPAT_BINFMT_ELF
	default y
	---help---
	  If enabled, the kernel will support running TILE-Gx binaries
	  that were built with the -m32 option.

213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228
config SECCOMP
	bool "Enable seccomp to safely compute untrusted bytecode"
	depends on PROC_FS
	help
	  This kernel feature is useful for number crunching applications
	  that may need to compute untrusted bytecode during their
	  execution. By using pipes or other transports made available to
	  the process as file descriptors supporting the read/write
	  syscalls, it's possible to isolate those applications in
	  their own address space using seccomp. Once seccomp is
	  enabled via prctl, it cannot be disabled and the task is only
	  allowed to execute a few safe syscalls defined by each seccomp
	  mode.

	  If unsure, say N.

229 230 231 232
config SYSVIPC_COMPAT
	def_bool y
	depends on COMPAT && SYSVIPC

233
# We do not currently support disabling HIGHMEM on tilepro.
234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251
config HIGHMEM
	bool # "Support for more than 512 MB of RAM"
	default !TILEGX
	---help---
	  Linux can use the full amount of RAM in the system by
	  default.  However, the address space of TILE processors is
	  only 4 Gigabytes large. That means that, if you have a large
	  amount of physical memory, not all of it can be "permanently
	  mapped" by the kernel. The physical memory that's not
	  permanently mapped is called "high memory".

	  If you are compiling a kernel which will never run on a
	  machine with more than 512 MB total physical RAM, answer
	  "false" here. This will result in the kernel mapping all of
	  physical memory into the top 1 GB of virtual memory space.

	  If unsure, say "true".

252
config ZONE_DMA32
253 254
	def_bool y

255 256 257 258 259 260 261 262 263
config IOMMU_HELPER
	bool

config NEED_SG_DMA_LENGTH
	bool

config SWIOTLB
	bool
	default TILEGX
264
	select DMA_DIRECT_OPS
265 266 267 268
	select IOMMU_HELPER
	select NEED_SG_DMA_LENGTH
	select ARCH_HAS_DMA_SET_COHERENT_MASK

269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289
# We do not currently support disabling NUMA.
config NUMA
	bool # "NUMA Memory Allocation and Scheduler Support"
	depends on SMP && DISCONTIGMEM
	default y
	---help---
	  NUMA memory allocation is required for TILE processors
	  unless booting with memory striping enabled in the
	  hypervisor, or with only a single memory controller.
	  It is recommended that this option always be enabled.

config NODES_SHIFT
	int "Log base 2 of the max number of memory controllers"
	default 2
	depends on NEED_MULTIPLE_NODES
	---help---
	  By default, 2, i.e. 2^2 == 4 DDR2 controllers.
	  In a system with more controllers, this value should be raised.

choice
	depends on !TILEGX
290
	prompt "Memory split" if EXPERT
291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307
	default VMSPLIT_3G
	---help---
	  Select the desired split between kernel and user memory.

	  If the address range available to the kernel is less than the
	  physical memory installed, the remaining memory will be available
	  as "high memory". Accessing high memory is a little more costly
	  than low memory, as it needs to be mapped into the kernel first.
	  Note that increasing the kernel address space limits the range
	  available to user programs, making the address space there
	  tighter.  Selecting anything other than the default 3G/1G split
	  will also likely make your kernel incompatible with binary-only
	  kernel modules.

	  If you are not absolutely sure what you are doing, leave this
	  option alone!

308
	config VMSPLIT_3_75G
309
		bool "3.75G/0.25G user/kernel split (no kernel networking)"
310
	config VMSPLIT_3_5G
311 312 313
		bool "3.5G/0.5G user/kernel split"
	config VMSPLIT_3G
		bool "3G/1G user/kernel split"
314 315 316 317 318 319
	config VMSPLIT_2_75G
		bool "2.75G/1.25G user/kernel split (for full 1G low memory)"
	config VMSPLIT_2_5G
		bool "2.5G/1.5G user/kernel split"
	config VMSPLIT_2_25G
		bool "2.25G/1.75G user/kernel split"
320 321 322 323 324 325 326 327
	config VMSPLIT_2G
		bool "2G/2G user/kernel split"
	config VMSPLIT_1G
		bool "1G/3G user/kernel split"
endchoice

config PAGE_OFFSET
	hex
328
	depends on !64BIT
329 330
	default 0xF0000000 if VMSPLIT_3_75G
	default 0xE0000000 if VMSPLIT_3_5G
331 332 333
	default 0xB0000000 if VMSPLIT_2_75G
	default 0xA0000000 if VMSPLIT_2_5G
	default 0x90000000 if VMSPLIT_2_25G
334 335 336 337 338 339
	default 0x80000000 if VMSPLIT_2G
	default 0x40000000 if VMSPLIT_1G
	default 0xC0000000

source "mm/Kconfig"

Chris Metcalf's avatar
Chris Metcalf committed
340 341
source "kernel/Kconfig.preempt"

342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388
config CMDLINE_BOOL
	bool "Built-in kernel command line"
	default n
	---help---
	  Allow for specifying boot arguments to the kernel at
	  build time.  On some systems (e.g. embedded ones), it is
	  necessary or convenient to provide some or all of the
	  kernel boot arguments with the kernel itself (that is,
	  to not rely on the boot loader to provide them.)

	  To compile command line arguments into the kernel,
	  set this option to 'Y', then fill in the
	  the boot arguments in CONFIG_CMDLINE.

	  Systems with fully functional boot loaders (e.g. mboot, or
	  if booting over PCI) should leave this option set to 'N'.

config CMDLINE
	string "Built-in kernel command string"
	depends on CMDLINE_BOOL
	default ""
	---help---
	  Enter arguments here that should be compiled into the kernel
	  image and used at boot time.  If the boot loader provides a
	  command line at boot time, it is appended to this string to
	  form the full kernel command line, when the system boots.

	  However, you can use the CONFIG_CMDLINE_OVERRIDE option to
	  change this behavior.

	  In most cases, the command line (whether built-in or provided
	  by the boot loader) should specify the device for the root
	  file system.

config CMDLINE_OVERRIDE
	bool "Built-in command line overrides boot loader arguments"
	default n
	depends on CMDLINE_BOOL
	---help---
	  Set this option to 'Y' to have the kernel ignore the boot loader
	  command line, and use ONLY the built-in command line.

	  This is used to work around broken boot loaders.  This should
	  be set to 'N' under normal conditions.

config VMALLOC_RESERVE
	hex
389
	default 0x2000000
390

391 392 393 394
config HARDWALL
	bool "Hardwall support to allow access to user dynamic network"
	default y

395 396 397
config KERNEL_PL
	int "Processor protection level for kernel"
	range 1 2
398 399
	default 2 if TILEGX
	default 1 if !TILEGX
400
	---help---
401 402 403 404 405 406 407 408
	  Since MDE 4.2, the Tilera hypervisor runs the kernel
	  at PL2 by default.  If running under an older hypervisor,
	  or as a KVM guest, you must run at PL1.  (The current
	  hypervisor may also be recompiled with "make HV_PL=2" to
	  allow it to run a kernel at PL1, but clients running at PL1
	  are not expected to be supported indefinitely.)

	  If you're not sure, don't change the default.
409

410 411
source "arch/tile/gxio/Kconfig"

412 413 414 415
endmenu  # Tilera-specific configuration

menu "Bus options"

416 417 418 419
config PCI
	bool "PCI support"
	default y
	select PCI_DOMAINS
420
	select GENERIC_PCI_IOMAP
421 422
	select TILE_GXIO_TRIO if TILEGX
	select PCI_MSI if TILEGX
423 424 425 426 427 428 429 430
	---help---
	  Enable PCI root complex support, so PCIe endpoint devices can
	  be attached to the Tile chip.  Many, but not all, PCI devices
	  are supported under Tilera's root complex driver.

config PCI_DOMAINS
	bool

431 432 433
config NO_IOMEM
	def_bool !PCI

434
config NO_IOPORT_MAP
435 436
	def_bool !PCI

437 438 439 440 441 442 443 444 445 446
config TILE_PCI_IO
	bool "PCI I/O space support"
	default n
	depends on PCI
	depends on TILEGX
	---help---
	  Enable PCI I/O space support on TILEGx. Since the PCI I/O space
	  is used by few modern PCIe endpoint devices, its support is disabled
	  by default to save the TRIO PIO Region resource for other purposes.

447 448
source "drivers/pci/Kconfig"

449 450 451 452 453 454 455 456 457 458
config TILE_USB
	tristate "Tilera USB host adapter support"
	default y
	depends on USB
	depends on TILEGX
	select TILE_GXIO_USB_HOST
	---help---
	  Provides USB host adapter support for the built-in EHCI and OHCI
	  interfaces on TILE-Gx chips.

459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479
endmenu

menu "Executable file formats"

source "fs/Kconfig.binfmt"

endmenu

source "net/Kconfig"

source "drivers/Kconfig"

source "fs/Kconfig"

source "arch/tile/Kconfig.debug"

source "security/Kconfig"

source "crypto/Kconfig"

source "lib/Kconfig"
480 481

source "arch/tile/kvm/Kconfig"