arch/tile/Kconfig

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