Version:  2.0.40 2.2.26 2.4.37 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17

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

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us