Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

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