xref: /openbmc/linux/arch/s390/Kconfig (revision 81d67439)
1config MMU
2	def_bool y
3
4config ZONE_DMA
5	def_bool y
6
7config LOCKDEP_SUPPORT
8	def_bool y
9
10config STACKTRACE_SUPPORT
11	def_bool y
12
13config HAVE_LATENCYTOP_SUPPORT
14	def_bool y
15
16config RWSEM_GENERIC_SPINLOCK
17	bool
18
19config RWSEM_XCHGADD_ALGORITHM
20	def_bool y
21
22config ARCH_HAS_ILOG2_U32
23	def_bool n
24
25config ARCH_HAS_ILOG2_U64
26	def_bool n
27
28config GENERIC_HWEIGHT
29	def_bool y
30
31config GENERIC_TIME_VSYSCALL
32	def_bool y
33
34config GENERIC_CLOCKEVENTS
35	def_bool y
36
37config GENERIC_BUG
38	def_bool y if BUG
39
40config GENERIC_BUG_RELATIVE_POINTERS
41	def_bool y
42
43config NO_IOMEM
44	def_bool y
45
46config NO_DMA
47	def_bool y
48
49config ARCH_DMA_ADDR_T_64BIT
50	def_bool 64BIT
51
52config GENERIC_LOCKBREAK
53	def_bool y if SMP && PREEMPT
54
55config PGSTE
56	def_bool y if KVM
57
58config VIRT_CPU_ACCOUNTING
59	def_bool y
60
61config ARCH_SUPPORTS_DEBUG_PAGEALLOC
62	def_bool y
63
64config S390
65	def_bool y
66	select USE_GENERIC_SMP_HELPERS if SMP
67	select HAVE_SYSCALL_WRAPPERS
68	select HAVE_FUNCTION_TRACER
69	select HAVE_FUNCTION_TRACE_MCOUNT_TEST
70	select HAVE_FTRACE_MCOUNT_RECORD
71	select HAVE_C_RECORDMCOUNT
72	select HAVE_SYSCALL_TRACEPOINTS
73	select HAVE_DYNAMIC_FTRACE
74	select HAVE_FUNCTION_GRAPH_TRACER
75	select HAVE_REGS_AND_STACK_ACCESS_API
76	select HAVE_OPROFILE
77	select HAVE_KPROBES
78	select HAVE_KRETPROBES
79	select HAVE_KVM if 64BIT
80	select HAVE_ARCH_TRACEHOOK
81	select INIT_ALL_POSSIBLE
82	select HAVE_IRQ_WORK
83	select HAVE_PERF_EVENTS
84	select HAVE_KERNEL_GZIP
85	select HAVE_KERNEL_BZIP2
86	select HAVE_KERNEL_LZMA
87	select HAVE_KERNEL_LZO
88	select HAVE_KERNEL_XZ
89	select HAVE_GET_USER_PAGES_FAST
90	select HAVE_ARCH_MUTEX_CPU_RELAX
91	select HAVE_ARCH_JUMP_LABEL if !MARCH_G5
92	select HAVE_RCU_TABLE_FREE if SMP
93	select ARCH_INLINE_SPIN_TRYLOCK
94	select ARCH_INLINE_SPIN_TRYLOCK_BH
95	select ARCH_INLINE_SPIN_LOCK
96	select ARCH_INLINE_SPIN_LOCK_BH
97	select ARCH_INLINE_SPIN_LOCK_IRQ
98	select ARCH_INLINE_SPIN_LOCK_IRQSAVE
99	select ARCH_INLINE_SPIN_UNLOCK
100	select ARCH_INLINE_SPIN_UNLOCK_BH
101	select ARCH_INLINE_SPIN_UNLOCK_IRQ
102	select ARCH_INLINE_SPIN_UNLOCK_IRQRESTORE
103	select ARCH_INLINE_READ_TRYLOCK
104	select ARCH_INLINE_READ_LOCK
105	select ARCH_INLINE_READ_LOCK_BH
106	select ARCH_INLINE_READ_LOCK_IRQ
107	select ARCH_INLINE_READ_LOCK_IRQSAVE
108	select ARCH_INLINE_READ_UNLOCK
109	select ARCH_INLINE_READ_UNLOCK_BH
110	select ARCH_INLINE_READ_UNLOCK_IRQ
111	select ARCH_INLINE_READ_UNLOCK_IRQRESTORE
112	select ARCH_INLINE_WRITE_TRYLOCK
113	select ARCH_INLINE_WRITE_LOCK
114	select ARCH_INLINE_WRITE_LOCK_BH
115	select ARCH_INLINE_WRITE_LOCK_IRQ
116	select ARCH_INLINE_WRITE_LOCK_IRQSAVE
117	select ARCH_INLINE_WRITE_UNLOCK
118	select ARCH_INLINE_WRITE_UNLOCK_BH
119	select ARCH_INLINE_WRITE_UNLOCK_IRQ
120	select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE
121
122config SCHED_OMIT_FRAME_POINTER
123	def_bool y
124
125source "init/Kconfig"
126
127source "kernel/Kconfig.freezer"
128
129menu "Base setup"
130
131comment "Processor type and features"
132
133source "kernel/time/Kconfig"
134
135config 64BIT
136	def_bool y
137	prompt "64 bit kernel"
138	help
139	  Select this option if you have an IBM z/Architecture machine
140	  and want to use the 64 bit addressing mode.
141
142config 32BIT
143	def_bool y if !64BIT
144
145config KTIME_SCALAR
146	def_bool 32BIT
147
148config SMP
149	def_bool y
150	prompt "Symmetric multi-processing support"
151	---help---
152	  This enables support for systems with more than one CPU. If you have
153	  a system with only one CPU, like most personal computers, say N. If
154	  you have a system with more than one CPU, say Y.
155
156	  If you say N here, the kernel will run on single and multiprocessor
157	  machines, but will use only one CPU of a multiprocessor machine. If
158	  you say Y here, the kernel will run on many, but not all,
159	  singleprocessor machines. On a singleprocessor machine, the kernel
160	  will run faster if you say N here.
161
162	  See also the SMP-HOWTO available at
163	  <http://www.tldp.org/docs.html#howto>.
164
165	  Even if you don't know what to do here, say Y.
166
167config NR_CPUS
168	int "Maximum number of CPUs (2-64)"
169	range 2 64
170	depends on SMP
171	default "32" if !64BIT
172	default "64" if 64BIT
173	help
174	  This allows you to specify the maximum number of CPUs which this
175	  kernel will support.  The maximum supported value is 64 and the
176	  minimum value which makes sense is 2.
177
178	  This is purely to save memory - each supported CPU adds
179	  approximately sixteen kilobytes to the kernel image.
180
181config HOTPLUG_CPU
182	def_bool y
183	prompt "Support for hot-pluggable CPUs"
184	depends on SMP
185	select HOTPLUG
186	help
187	  Say Y here to be able to turn CPUs off and on. CPUs
188	  can be controlled through /sys/devices/system/cpu/cpu#.
189	  Say N if you want to disable CPU hotplug.
190
191config SCHED_MC
192	def_bool y
193	prompt "Multi-core scheduler support"
194	depends on SMP
195	help
196	  Multi-core scheduler support improves the CPU scheduler's decision
197	  making when dealing with multi-core CPU chips at a cost of slightly
198	  increased overhead in some places.
199
200config SCHED_BOOK
201	def_bool y
202	prompt "Book scheduler support"
203	depends on SMP && SCHED_MC
204	help
205	  Book scheduler support improves the CPU scheduler's decision making
206	  when dealing with machines that have several books.
207
208config MATHEMU
209	def_bool y
210	prompt "IEEE FPU emulation"
211	depends on MARCH_G5
212	help
213	  This option is required for IEEE compliant floating point arithmetic
214	  on older ESA/390 machines. Say Y unless you know your machine doesn't
215	  need this.
216
217config COMPAT
218	def_bool y
219	prompt "Kernel support for 31 bit emulation"
220	depends on 64BIT
221	select COMPAT_BINFMT_ELF
222	help
223	  Select this option if you want to enable your system kernel to
224	  handle system-calls from ELF binaries for 31 bit ESA.  This option
225	  (and some other stuff like libraries and such) is needed for
226	  executing 31 bit applications.  It is safe to say "Y".
227
228config SYSVIPC_COMPAT
229	def_bool y if COMPAT && SYSVIPC
230
231config AUDIT_ARCH
232	def_bool y
233
234comment "Code generation options"
235
236choice
237	prompt "Processor type"
238	default MARCH_G5
239
240config MARCH_G5
241	bool "System/390 model G5 and G6"
242	depends on !64BIT
243	help
244	  Select this to build a 31 bit kernel that works
245	  on all ESA/390 and z/Architecture machines.
246
247config MARCH_Z900
248	bool "IBM zSeries model z800 and z900"
249	help
250	  Select this to enable optimizations for model z800/z900 (2064 and
251	  2066 series). This will enable some optimizations that are not
252	  available on older ESA/390 (31 Bit) only CPUs.
253
254config MARCH_Z990
255	bool "IBM zSeries model z890 and z990"
256	help
257	  Select this to enable optimizations for model z890/z990 (2084 and
258	  2086 series). The kernel will be slightly faster but will not work
259	  on older machines.
260
261config MARCH_Z9_109
262	bool "IBM System z9"
263	help
264	  Select this to enable optimizations for IBM System z9 (2094 and
265	  2096 series). The kernel will be slightly faster but will not work
266	  on older machines.
267
268config MARCH_Z10
269	bool "IBM System z10"
270	help
271	  Select this to enable optimizations for IBM System z10 (2097 and
272	  2098 series). The kernel will be slightly faster but will not work
273	  on older machines.
274
275config MARCH_Z196
276	bool "IBM zEnterprise 196"
277	help
278	  Select this to enable optimizations for IBM zEnterprise 196
279	  (2817 series). The kernel will be slightly faster but will not work
280	  on older machines.
281
282endchoice
283
284config PACK_STACK
285	def_bool y
286	prompt "Pack kernel stack"
287	help
288	  This option enables the compiler option -mkernel-backchain if it
289	  is available. If the option is available the compiler supports
290	  the new stack layout which dramatically reduces the minimum stack
291	  frame size. With an old compiler a non-leaf function needs a
292	  minimum of 96 bytes on 31 bit and 160 bytes on 64 bit. With
293	  -mkernel-backchain the minimum size drops to 16 byte on 31 bit
294	  and 24 byte on 64 bit.
295
296	  Say Y if you are unsure.
297
298config SMALL_STACK
299	def_bool n
300	prompt "Use 8kb for kernel stack instead of 16kb"
301	depends on PACK_STACK && 64BIT && !LOCKDEP
302	help
303	  If you say Y here and the compiler supports the -mkernel-backchain
304	  option the kernel will use a smaller kernel stack size. The reduced
305	  size is 8kb instead of 16kb. This allows to run more threads on a
306	  system and reduces the pressure on the memory management for higher
307	  order page allocations.
308
309	  Say N if you are unsure.
310
311config CHECK_STACK
312	def_bool y
313	prompt "Detect kernel stack overflow"
314	help
315	  This option enables the compiler option -mstack-guard and
316	  -mstack-size if they are available. If the compiler supports them
317	  it will emit additional code to each function prolog to trigger
318	  an illegal operation if the kernel stack is about to overflow.
319
320	  Say N if you are unsure.
321
322config STACK_GUARD
323	int "Size of the guard area (128-1024)"
324	range 128 1024
325	depends on CHECK_STACK
326	default "256"
327	help
328	  This allows you to specify the size of the guard area at the lower
329	  end of the kernel stack. If the kernel stack points into the guard
330	  area on function entry an illegal operation is triggered. The size
331	  needs to be a power of 2. Please keep in mind that the size of an
332	  interrupt frame is 184 bytes for 31 bit and 328 bytes on 64 bit.
333	  The minimum size for the stack guard should be 256 for 31 bit and
334	  512 for 64 bit.
335
336config WARN_DYNAMIC_STACK
337	def_bool n
338	prompt "Emit compiler warnings for function with dynamic stack usage"
339	help
340	  This option enables the compiler option -mwarn-dynamicstack. If the
341	  compiler supports this options generates warnings for functions
342	  that dynamically allocate stack space using alloca.
343
344	  Say N if you are unsure.
345
346config ARCH_POPULATES_NODE_MAP
347	def_bool y
348
349comment "Kernel preemption"
350
351source "kernel/Kconfig.preempt"
352
353config ARCH_SPARSEMEM_ENABLE
354	def_bool y
355	select SPARSEMEM_VMEMMAP_ENABLE
356	select SPARSEMEM_VMEMMAP
357	select SPARSEMEM_STATIC if !64BIT
358
359config ARCH_SPARSEMEM_DEFAULT
360	def_bool y
361
362config ARCH_SELECT_MEMORY_MODEL
363	def_bool y
364
365config ARCH_ENABLE_MEMORY_HOTPLUG
366	def_bool y if SPARSEMEM
367
368config ARCH_ENABLE_MEMORY_HOTREMOVE
369	def_bool y
370
371config ARCH_HIBERNATION_POSSIBLE
372	def_bool y if 64BIT
373
374source "mm/Kconfig"
375
376comment "I/O subsystem configuration"
377
378config QDIO
379	def_tristate y
380	prompt "QDIO support"
381	---help---
382	  This driver provides the Queued Direct I/O base support for
383	  IBM System z.
384
385	  To compile this driver as a module, choose M here: the
386	  module will be called qdio.
387
388	  If unsure, say Y.
389
390config CHSC_SCH
391	def_tristate m
392	prompt "Support for CHSC subchannels"
393	help
394	  This driver allows usage of CHSC subchannels. A CHSC subchannel
395	  is usually present on LPAR only.
396	  The driver creates a device /dev/chsc, which may be used to
397	  obtain I/O configuration information about the machine and
398	  to issue asynchronous chsc commands (DANGEROUS).
399	  You will usually only want to use this interface on a special
400	  LPAR designated for system management.
401
402	  To compile this driver as a module, choose M here: the
403	  module will be called chsc_sch.
404
405	  If unsure, say N.
406
407comment "Misc"
408
409config IPL
410	def_bool y
411	prompt "Builtin IPL record support"
412	help
413	  If you want to use the produced kernel to IPL directly from a
414	  device, you have to merge a bootsector specific to the device
415	  into the first bytes of the kernel. You will have to select the
416	  IPL device.
417
418choice
419	prompt "IPL method generated into head.S"
420	depends on IPL
421	default IPL_VM
422	help
423	  Select "tape" if you want to IPL the image from a Tape.
424
425	  Select "vm_reader" if you are running under VM/ESA and want
426	  to IPL the image from the emulated card reader.
427
428config IPL_TAPE
429	bool "tape"
430
431config IPL_VM
432	bool "vm_reader"
433
434endchoice
435
436source "fs/Kconfig.binfmt"
437
438config FORCE_MAX_ZONEORDER
439	int
440	default "9"
441
442config PFAULT
443	def_bool y
444	prompt "Pseudo page fault support"
445	help
446	  Select this option, if you want to use PFAULT pseudo page fault
447	  handling under VM. If running native or in LPAR, this option
448	  has no effect. If your VM does not support PFAULT, PAGEEX
449	  pseudo page fault handling will be used.
450	  Note that VM 4.2 supports PFAULT but has a bug in its
451	  implementation that causes some problems.
452	  Everybody who wants to run Linux under VM != VM4.2 should select
453	  this option.
454
455config SHARED_KERNEL
456	def_bool y
457	prompt "VM shared kernel support"
458	help
459	  Select this option, if you want to share the text segment of the
460	  Linux kernel between different VM guests. This reduces memory
461	  usage with lots of guests but greatly increases kernel size.
462	  Also if a kernel was IPL'ed from a shared segment the kexec system
463	  call will not work.
464	  You should only select this option if you know what you are
465	  doing and want to exploit this feature.
466
467config CMM
468	def_tristate n
469	prompt "Cooperative memory management"
470	help
471	  Select this option, if you want to enable the kernel interface
472	  to reduce the memory size of the system. This is accomplished
473	  by allocating pages of memory and put them "on hold". This only
474	  makes sense for a system running under VM where the unused pages
475	  will be reused by VM for other guest systems. The interface
476	  allows an external monitor to balance memory of many systems.
477	  Everybody who wants to run Linux under VM should select this
478	  option.
479
480config CMM_IUCV
481	def_bool y
482	prompt "IUCV special message interface to cooperative memory management"
483	depends on CMM && (SMSGIUCV=y || CMM=SMSGIUCV)
484	help
485	  Select this option to enable the special message interface to
486	  the cooperative memory management.
487
488config APPLDATA_BASE
489	def_bool n
490	prompt "Linux - VM Monitor Stream, base infrastructure"
491	depends on PROC_FS
492	help
493	  This provides a kernel interface for creating and updating z/VM APPLDATA
494	  monitor records. The monitor records are updated at certain time
495	  intervals, once the timer is started.
496	  Writing 1 or 0 to /proc/appldata/timer starts(1) or stops(0) the timer,
497	  i.e. enables or disables monitoring on the Linux side.
498	  A custom interval value (in seconds) can be written to
499	  /proc/appldata/interval.
500
501	  Defaults are 60 seconds interval and timer off.
502	  The /proc entries can also be read from, showing the current settings.
503
504config APPLDATA_MEM
505	def_tristate m
506	prompt "Monitor memory management statistics"
507	depends on APPLDATA_BASE && VM_EVENT_COUNTERS
508	help
509	  This provides memory management related data to the Linux - VM Monitor
510	  Stream, like paging/swapping rate, memory utilisation, etc.
511	  Writing 1 or 0 to /proc/appldata/memory creates(1) or removes(0) a z/VM
512	  APPLDATA monitor record, i.e. enables or disables monitoring this record
513	  on the z/VM side.
514
515	  Default is disabled.
516	  The /proc entry can also be read from, showing the current settings.
517
518	  This can also be compiled as a module, which will be called
519	  appldata_mem.o.
520
521config APPLDATA_OS
522	def_tristate m
523	prompt "Monitor OS statistics"
524	depends on APPLDATA_BASE
525	help
526	  This provides OS related data to the Linux - VM Monitor Stream, like
527	  CPU utilisation, etc.
528	  Writing 1 or 0 to /proc/appldata/os creates(1) or removes(0) a z/VM
529	  APPLDATA monitor record, i.e. enables or disables monitoring this record
530	  on the z/VM side.
531
532	  Default is disabled.
533	  This can also be compiled as a module, which will be called
534	  appldata_os.o.
535
536config APPLDATA_NET_SUM
537	def_tristate m
538	prompt "Monitor overall network statistics"
539	depends on APPLDATA_BASE && NET
540	help
541	  This provides network related data to the Linux - VM Monitor Stream,
542	  currently there is only a total sum of network I/O statistics, no
543	  per-interface data.
544	  Writing 1 or 0 to /proc/appldata/net_sum creates(1) or removes(0) a z/VM
545	  APPLDATA monitor record, i.e. enables or disables monitoring this record
546	  on the z/VM side.
547
548	  Default is disabled.
549	  This can also be compiled as a module, which will be called
550	  appldata_net_sum.o.
551
552source kernel/Kconfig.hz
553
554config S390_HYPFS_FS
555	def_bool y
556	prompt "s390 hypervisor file system support"
557	select SYS_HYPERVISOR
558	help
559	  This is a virtual file system intended to provide accounting
560	  information in an s390 hypervisor environment.
561
562config KEXEC
563	def_bool n
564	prompt "kexec system call"
565	help
566	  kexec is a system call that implements the ability to shutdown your
567	  current kernel, and to start another kernel.  It is like a reboot
568	  but is independent of hardware/microcode support.
569
570config ZFCPDUMP
571	def_bool n
572	prompt "zfcpdump support"
573	select SMP
574	help
575	  Select this option if you want to build an zfcpdump enabled kernel.
576	  Refer to <file:Documentation/s390/zfcpdump.txt> for more details on this.
577
578config S390_GUEST
579	def_bool y
580	prompt "s390 guest support for KVM (EXPERIMENTAL)"
581	depends on 64BIT && EXPERIMENTAL
582	select VIRTUALIZATION
583	select VIRTIO
584	select VIRTIO_RING
585	select VIRTIO_CONSOLE
586	help
587	  Select this option if you want to run the kernel as a guest under
588	  the KVM hypervisor. This will add detection for KVM as well  as a
589	  virtio transport. If KVM is detected, the virtio console will be
590	  the default console.
591
592config SECCOMP
593	def_bool y
594	prompt "Enable seccomp to safely compute untrusted bytecode"
595	depends on PROC_FS
596	help
597	  This kernel feature is useful for number crunching applications
598	  that may need to compute untrusted bytecode during their
599	  execution. By using pipes or other transports made available to
600	  the process as file descriptors supporting the read/write
601	  syscalls, it's possible to isolate those applications in
602	  their own address space using seccomp. Once seccomp is
603	  enabled via /proc/<pid>/seccomp, it cannot be disabled
604	  and the task is only allowed to execute a few safe syscalls
605	  defined by each seccomp mode.
606
607	  If unsure, say Y.
608
609endmenu
610
611menu "Power Management"
612
613source "kernel/power/Kconfig"
614
615endmenu
616
617source "net/Kconfig"
618
619config PCMCIA
620	def_bool n
621
622config CCW
623	def_bool y
624
625source "drivers/Kconfig"
626
627source "fs/Kconfig"
628
629source "arch/s390/Kconfig.debug"
630
631source "security/Kconfig"
632
633source "crypto/Kconfig"
634
635source "lib/Kconfig"
636
637source "arch/s390/kvm/Kconfig"
638