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