• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1config ARM64
2	def_bool y
3	select ACPI_CCA_REQUIRED if ACPI
4	select ACPI_GENERIC_GSI if ACPI
5	select ACPI_REDUCED_HARDWARE_ONLY if ACPI
6	select ACPI_MCFG if ACPI
7	select ACPI_SPCR_TABLE if ACPI
8	select ARCH_CLOCKSOURCE_DATA
9	select ARCH_HAS_DEVMEM_IS_ALLOWED
10	select ARCH_HAS_ACPI_TABLE_UPGRADE if ACPI
11	select ARCH_HAS_ELF_RANDOMIZE
12	select ARCH_HAS_GCOV_PROFILE_ALL
13	select ARCH_HAS_GIGANTIC_PAGE
14	select ARCH_HAS_KCOV
15	select ARCH_HAS_SG_CHAIN
16	select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST
17	select ARCH_USE_CMPXCHG_LOCKREF
18	select ARCH_SUPPORTS_LTO_CLANG
19	select ARCH_SUPPORTS_ATOMIC_RMW
20	select ARCH_SUPPORTS_NUMA_BALANCING
21	select ARCH_WANT_COMPAT_IPC_PARSE_VERSION
22	select ARCH_WANT_FRAME_POINTERS
23	select ARCH_HAS_UBSAN_SANITIZE_ALL
24	select ARM_AMBA
25	select ARM_ARCH_TIMER
26	select ARM_GIC
27	select AUDIT_ARCH_COMPAT_GENERIC
28	select ARM_GIC_V2M if PCI
29	select ARM_GIC_V3
30	select ARM_GIC_V3_ITS if PCI
31	select ARM_PSCI_FW
32	select BUILDTIME_EXTABLE_SORT
33	select CLONE_BACKWARDS
34	select COMMON_CLK
35	select CPU_PM if (SUSPEND || CPU_IDLE)
36	select DCACHE_WORD_ACCESS
37	select EDAC_SUPPORT
38	select FRAME_POINTER
39	select GENERIC_ALLOCATOR
40	select GENERIC_CLOCKEVENTS
41	select GENERIC_CLOCKEVENTS_BROADCAST
42	select GENERIC_CPU_AUTOPROBE
43	select GENERIC_EARLY_IOREMAP
44	select GENERIC_IDLE_POLL_SETUP
45	select GENERIC_IRQ_PROBE
46	select GENERIC_IRQ_SHOW
47	select GENERIC_IRQ_SHOW_LEVEL
48	select GENERIC_PCI_IOMAP
49	select GENERIC_SCHED_CLOCK
50	select GENERIC_SMP_IDLE_THREAD
51	select GENERIC_STRNCPY_FROM_USER
52	select GENERIC_STRNLEN_USER
53	select GENERIC_TIME_VSYSCALL
54	select HANDLE_DOMAIN_IRQ
55	select HARDIRQS_SW_RESEND
56	select HAVE_ALIGNED_STRUCT_PAGE if SLUB
57	select HAVE_ARCH_AUDITSYSCALL
58	select HAVE_ARCH_BITREVERSE
59	select HAVE_ARCH_HARDENED_USERCOPY
60	select HAVE_ARCH_HUGE_VMAP
61	select HAVE_ARCH_JUMP_LABEL
62	select HAVE_ARCH_KASAN if SPARSEMEM_VMEMMAP && !(ARM64_16K_PAGES && ARM64_VA_BITS_48)
63	select HAVE_ARCH_KGDB
64	select HAVE_ARCH_MMAP_RND_BITS
65	select HAVE_ARCH_MMAP_RND_COMPAT_BITS if COMPAT
66	select HAVE_ARCH_SECCOMP_FILTER
67	select HAVE_ARCH_TRACEHOOK
68	select HAVE_ARCH_TRANSPARENT_HUGEPAGE
69	select HAVE_ARM_SMCCC
70	select HAVE_EBPF_JIT
71	select HAVE_C_RECORDMCOUNT
72	select HAVE_CC_STACKPROTECTOR
73	select HAVE_CMPXCHG_DOUBLE
74	select HAVE_CMPXCHG_LOCAL
75	select HAVE_CONTEXT_TRACKING
76	select HAVE_DEBUG_BUGVERBOSE
77	select HAVE_DEBUG_KMEMLEAK
78	select HAVE_DMA_API_DEBUG
79	select HAVE_DMA_CONTIGUOUS
80	select HAVE_DYNAMIC_FTRACE
81	select HAVE_EFFICIENT_UNALIGNED_ACCESS
82	select HAVE_FTRACE_MCOUNT_RECORD
83	select HAVE_FUNCTION_TRACER
84	select HAVE_FUNCTION_GRAPH_TRACER
85	select HAVE_GCC_PLUGINS
86	select HAVE_GENERIC_DMA_COHERENT
87	select HAVE_HW_BREAKPOINT if PERF_EVENTS
88	select HAVE_IRQ_TIME_ACCOUNTING
89	select HAVE_MEMBLOCK
90	select HAVE_MEMBLOCK_NODE_MAP if NUMA
91	select HAVE_PATA_PLATFORM
92	select HAVE_PERF_EVENTS
93	select HAVE_PERF_REGS
94	select HAVE_PERF_USER_STACK_DUMP
95	select HAVE_REGS_AND_STACK_ACCESS_API
96	select HAVE_RCU_TABLE_FREE
97	select HAVE_SYSCALL_TRACEPOINTS
98	select HAVE_KPROBES
99	select HAVE_KRETPROBES if HAVE_KPROBES
100	select IOMMU_DMA if IOMMU_SUPPORT
101	select IRQ_DOMAIN
102	select IRQ_FORCED_THREADING
103	select MODULES_USE_ELF_RELA
104	select NO_BOOTMEM
105	select OF
106	select OF_EARLY_FLATTREE
107	select OF_RESERVED_MEM
108	select PCI_ECAM if ACPI
109	select POWER_RESET
110	select POWER_SUPPLY
111	select SPARSE_IRQ
112	select SYSCTL_EXCEPTION_TRACE
113	select THREAD_INFO_IN_TASK
114	help
115	  ARM 64-bit (AArch64) Linux support.
116
117config 64BIT
118	def_bool y
119
120config ARCH_PHYS_ADDR_T_64BIT
121	def_bool y
122
123config MMU
124	def_bool y
125
126config DEBUG_RODATA
127	def_bool y
128
129config ARM64_PAGE_SHIFT
130	int
131	default 16 if ARM64_64K_PAGES
132	default 14 if ARM64_16K_PAGES
133	default 12
134
135config ARM64_CONT_SHIFT
136	int
137	default 5 if ARM64_64K_PAGES
138	default 7 if ARM64_16K_PAGES
139	default 4
140
141config ARCH_MMAP_RND_BITS_MIN
142       default 14 if ARM64_64K_PAGES
143       default 16 if ARM64_16K_PAGES
144       default 18
145
146# max bits determined by the following formula:
147#  VA_BITS - PAGE_SHIFT - 3
148config ARCH_MMAP_RND_BITS_MAX
149       default 19 if ARM64_VA_BITS=36
150       default 24 if ARM64_VA_BITS=39
151       default 27 if ARM64_VA_BITS=42
152       default 30 if ARM64_VA_BITS=47
153       default 29 if ARM64_VA_BITS=48 && ARM64_64K_PAGES
154       default 31 if ARM64_VA_BITS=48 && ARM64_16K_PAGES
155       default 33 if ARM64_VA_BITS=48
156       default 14 if ARM64_64K_PAGES
157       default 16 if ARM64_16K_PAGES
158       default 18
159
160config ARCH_MMAP_RND_COMPAT_BITS_MIN
161       default 7 if ARM64_64K_PAGES
162       default 9 if ARM64_16K_PAGES
163       default 11
164
165config ARCH_MMAP_RND_COMPAT_BITS_MAX
166       default 16
167
168config NO_IOPORT_MAP
169	def_bool y if !PCI
170
171config STACKTRACE_SUPPORT
172	def_bool y
173
174config ILLEGAL_POINTER_VALUE
175	hex
176	default 0xdead000000000000
177
178config LOCKDEP_SUPPORT
179	def_bool y
180
181config TRACE_IRQFLAGS_SUPPORT
182	def_bool y
183
184config RWSEM_XCHGADD_ALGORITHM
185	def_bool y
186
187config GENERIC_BUG
188	def_bool y
189	depends on BUG
190
191config GENERIC_BUG_RELATIVE_POINTERS
192	def_bool y
193	depends on GENERIC_BUG
194
195config GENERIC_HWEIGHT
196	def_bool y
197
198config GENERIC_CSUM
199        def_bool y
200
201config GENERIC_CALIBRATE_DELAY
202	def_bool y
203
204config ZONE_DMA
205	def_bool y
206
207config HAVE_GENERIC_RCU_GUP
208	def_bool y
209
210config ARCH_DMA_ADDR_T_64BIT
211	def_bool y
212
213config NEED_DMA_MAP_STATE
214	def_bool y
215
216config NEED_SG_DMA_LENGTH
217	def_bool y
218
219config SMP
220	def_bool y
221
222config SWIOTLB
223	def_bool y
224
225config IOMMU_HELPER
226	def_bool SWIOTLB
227
228config KERNEL_MODE_NEON
229	def_bool y
230
231config FIX_EARLYCON_MEM
232	def_bool y
233
234config PGTABLE_LEVELS
235	int
236	default 2 if ARM64_16K_PAGES && ARM64_VA_BITS_36
237	default 2 if ARM64_64K_PAGES && ARM64_VA_BITS_42
238	default 3 if ARM64_64K_PAGES && ARM64_VA_BITS_48
239	default 3 if ARM64_4K_PAGES && ARM64_VA_BITS_39
240	default 3 if ARM64_16K_PAGES && ARM64_VA_BITS_47
241	default 4 if !ARM64_64K_PAGES && ARM64_VA_BITS_48
242
243source "init/Kconfig"
244
245source "kernel/Kconfig.freezer"
246
247source "arch/arm64/Kconfig.platforms"
248
249menu "Bus support"
250
251config PCI
252	bool "PCI support"
253	help
254	  This feature enables support for PCI bus system. If you say Y
255	  here, the kernel will include drivers and infrastructure code
256	  to support PCI bus devices.
257
258config PCI_DOMAINS
259	def_bool PCI
260
261config PCI_DOMAINS_GENERIC
262	def_bool PCI
263
264config PCI_SYSCALL
265	def_bool PCI
266
267source "drivers/pci/Kconfig"
268
269endmenu
270
271menu "Kernel Features"
272
273menu "ARM errata workarounds via the alternatives framework"
274
275config ARM64_ERRATUM_826319
276	bool "Cortex-A53: 826319: System might deadlock if a write cannot complete until read data is accepted"
277	default y
278	help
279	  This option adds an alternative code sequence to work around ARM
280	  erratum 826319 on Cortex-A53 parts up to r0p2 with an AMBA 4 ACE or
281	  AXI master interface and an L2 cache.
282
283	  If a Cortex-A53 uses an AMBA AXI4 ACE interface to other processors
284	  and is unable to accept a certain write via this interface, it will
285	  not progress on read data presented on the read data channel and the
286	  system can deadlock.
287
288	  The workaround promotes data cache clean instructions to
289	  data cache clean-and-invalidate.
290	  Please note that this does not necessarily enable the workaround,
291	  as it depends on the alternative framework, which will only patch
292	  the kernel if an affected CPU is detected.
293
294	  If unsure, say Y.
295
296config ARM64_ERRATUM_827319
297	bool "Cortex-A53: 827319: Data cache clean instructions might cause overlapping transactions to the interconnect"
298	default y
299	help
300	  This option adds an alternative code sequence to work around ARM
301	  erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI
302	  master interface and an L2 cache.
303
304	  Under certain conditions this erratum can cause a clean line eviction
305	  to occur at the same time as another transaction to the same address
306	  on the AMBA 5 CHI interface, which can cause data corruption if the
307	  interconnect reorders the two transactions.
308
309	  The workaround promotes data cache clean instructions to
310	  data cache clean-and-invalidate.
311	  Please note that this does not necessarily enable the workaround,
312	  as it depends on the alternative framework, which will only patch
313	  the kernel if an affected CPU is detected.
314
315	  If unsure, say Y.
316
317config ARM64_ERRATUM_824069
318	bool "Cortex-A53: 824069: Cache line might not be marked as clean after a CleanShared snoop"
319	default y
320	help
321	  This option adds an alternative code sequence to work around ARM
322	  erratum 824069 on Cortex-A53 parts up to r0p2 when it is connected
323	  to a coherent interconnect.
324
325	  If a Cortex-A53 processor is executing a store or prefetch for
326	  write instruction at the same time as a processor in another
327	  cluster is executing a cache maintenance operation to the same
328	  address, then this erratum might cause a clean cache line to be
329	  incorrectly marked as dirty.
330
331	  The workaround promotes data cache clean instructions to
332	  data cache clean-and-invalidate.
333	  Please note that this option does not necessarily enable the
334	  workaround, as it depends on the alternative framework, which will
335	  only patch the kernel if an affected CPU is detected.
336
337	  If unsure, say Y.
338
339config ARM64_ERRATUM_819472
340	bool "Cortex-A53: 819472: Store exclusive instructions might cause data corruption"
341	default y
342	help
343	  This option adds an alternative code sequence to work around ARM
344	  erratum 819472 on Cortex-A53 parts up to r0p1 with an L2 cache
345	  present when it is connected to a coherent interconnect.
346
347	  If the processor is executing a load and store exclusive sequence at
348	  the same time as a processor in another cluster is executing a cache
349	  maintenance operation to the same address, then this erratum might
350	  cause data corruption.
351
352	  The workaround promotes data cache clean instructions to
353	  data cache clean-and-invalidate.
354	  Please note that this does not necessarily enable the workaround,
355	  as it depends on the alternative framework, which will only patch
356	  the kernel if an affected CPU is detected.
357
358	  If unsure, say Y.
359
360config ARM64_ERRATUM_832075
361	bool "Cortex-A57: 832075: possible deadlock on mixing exclusive memory accesses with device loads"
362	default y
363	help
364	  This option adds an alternative code sequence to work around ARM
365	  erratum 832075 on Cortex-A57 parts up to r1p2.
366
367	  Affected Cortex-A57 parts might deadlock when exclusive load/store
368	  instructions to Write-Back memory are mixed with Device loads.
369
370	  The workaround is to promote device loads to use Load-Acquire
371	  semantics.
372	  Please note that this does not necessarily enable the workaround,
373	  as it depends on the alternative framework, which will only patch
374	  the kernel if an affected CPU is detected.
375
376	  If unsure, say Y.
377
378config ARM64_ERRATUM_834220
379	bool "Cortex-A57: 834220: Stage 2 translation fault might be incorrectly reported in presence of a Stage 1 fault"
380	depends on KVM
381	default y
382	help
383	  This option adds an alternative code sequence to work around ARM
384	  erratum 834220 on Cortex-A57 parts up to r1p2.
385
386	  Affected Cortex-A57 parts might report a Stage 2 translation
387	  fault as the result of a Stage 1 fault for load crossing a
388	  page boundary when there is a permission or device memory
389	  alignment fault at Stage 1 and a translation fault at Stage 2.
390
391	  The workaround is to verify that the Stage 1 translation
392	  doesn't generate a fault before handling the Stage 2 fault.
393	  Please note that this does not necessarily enable the workaround,
394	  as it depends on the alternative framework, which will only patch
395	  the kernel if an affected CPU is detected.
396
397	  If unsure, say Y.
398
399config ARM64_ERRATUM_845719
400	bool "Cortex-A53: 845719: a load might read incorrect data"
401	depends on COMPAT
402	default y
403	help
404	  This option adds an alternative code sequence to work around ARM
405	  erratum 845719 on Cortex-A53 parts up to r0p4.
406
407	  When running a compat (AArch32) userspace on an affected Cortex-A53
408	  part, a load at EL0 from a virtual address that matches the bottom 32
409	  bits of the virtual address used by a recent load at (AArch64) EL1
410	  might return incorrect data.
411
412	  The workaround is to write the contextidr_el1 register on exception
413	  return to a 32-bit task.
414	  Please note that this does not necessarily enable the workaround,
415	  as it depends on the alternative framework, which will only patch
416	  the kernel if an affected CPU is detected.
417
418	  If unsure, say Y.
419
420config ARM64_ERRATUM_843419
421	bool "Cortex-A53: 843419: A load or store might access an incorrect address"
422	default y if !LTO_CLANG
423	select ARM64_MODULE_CMODEL_LARGE if MODULES
424	help
425	  This option links the kernel with '--fix-cortex-a53-843419' and
426	  builds modules using the large memory model in order to avoid the use
427	  of the ADRP instruction, which can cause a subsequent memory access
428	  to use an incorrect address on Cortex-A53 parts up to r0p4.
429
430	  If unsure, say Y.
431
432config CAVIUM_ERRATUM_22375
433	bool "Cavium erratum 22375, 24313"
434	default y
435	help
436	  Enable workaround for erratum 22375, 24313.
437
438	  This implements two gicv3-its errata workarounds for ThunderX. Both
439	  with small impact affecting only ITS table allocation.
440
441	    erratum 22375: only alloc 8MB table size
442	    erratum 24313: ignore memory access type
443
444	  The fixes are in ITS initialization and basically ignore memory access
445	  type and table size provided by the TYPER and BASER registers.
446
447	  If unsure, say Y.
448
449config CAVIUM_ERRATUM_23144
450	bool "Cavium erratum 23144: ITS SYNC hang on dual socket system"
451	depends on NUMA
452	default y
453	help
454	  ITS SYNC command hang for cross node io and collections/cpu mapping.
455
456	  If unsure, say Y.
457
458config CAVIUM_ERRATUM_23154
459	bool "Cavium erratum 23154: Access to ICC_IAR1_EL1 is not sync'ed"
460	default y
461	help
462	  The gicv3 of ThunderX requires a modified version for
463	  reading the IAR status to ensure data synchronization
464	  (access to icc_iar1_el1 is not sync'ed before and after).
465
466	  If unsure, say Y.
467
468config CAVIUM_ERRATUM_27456
469	bool "Cavium erratum 27456: Broadcast TLBI instructions may cause icache corruption"
470	default y
471	help
472	  On ThunderX T88 pass 1.x through 2.1 parts, broadcast TLBI
473	  instructions may cause the icache to become corrupted if it
474	  contains data for a non-current ASID.  The fix is to
475	  invalidate the icache when changing the mm context.
476
477	  If unsure, say Y.
478
479config QCOM_QDF2400_ERRATUM_0065
480	bool "QDF2400 E0065: Incorrect GITS_TYPER.ITT_Entry_size"
481	default y
482	help
483	  On Qualcomm Datacenter Technologies QDF2400 SoC, ITS hardware reports
484	  ITE size incorrectly. The GITS_TYPER.ITT_Entry_size field should have
485	  been indicated as 16Bytes (0xf), not 8Bytes (0x7).
486
487	  If unsure, say Y.
488
489endmenu
490
491
492choice
493	prompt "Page size"
494	default ARM64_4K_PAGES
495	help
496	  Page size (translation granule) configuration.
497
498config ARM64_4K_PAGES
499	bool "4KB"
500	help
501	  This feature enables 4KB pages support.
502
503config ARM64_16K_PAGES
504	bool "16KB"
505	help
506	  The system will use 16KB pages support. AArch32 emulation
507	  requires applications compiled with 16K (or a multiple of 16K)
508	  aligned segments.
509
510config ARM64_64K_PAGES
511	bool "64KB"
512	help
513	  This feature enables 64KB pages support (4KB by default)
514	  allowing only two levels of page tables and faster TLB
515	  look-up. AArch32 emulation requires applications compiled
516	  with 64K aligned segments.
517
518endchoice
519
520choice
521	prompt "Virtual address space size"
522	default ARM64_VA_BITS_39 if ARM64_4K_PAGES
523	default ARM64_VA_BITS_47 if ARM64_16K_PAGES
524	default ARM64_VA_BITS_42 if ARM64_64K_PAGES
525	help
526	  Allows choosing one of multiple possible virtual address
527	  space sizes. The level of translation table is determined by
528	  a combination of page size and virtual address space size.
529
530config ARM64_VA_BITS_36
531	bool "36-bit" if EXPERT
532	depends on ARM64_16K_PAGES
533
534config ARM64_VA_BITS_39
535	bool "39-bit"
536	depends on ARM64_4K_PAGES
537
538config ARM64_VA_BITS_42
539	bool "42-bit"
540	depends on ARM64_64K_PAGES
541
542config ARM64_VA_BITS_47
543	bool "47-bit"
544	depends on ARM64_16K_PAGES
545
546config ARM64_VA_BITS_48
547	bool "48-bit"
548
549endchoice
550
551config ARM64_VA_BITS
552	int
553	default 36 if ARM64_VA_BITS_36
554	default 39 if ARM64_VA_BITS_39
555	default 42 if ARM64_VA_BITS_42
556	default 47 if ARM64_VA_BITS_47
557	default 48 if ARM64_VA_BITS_48
558
559config CPU_BIG_ENDIAN
560       bool "Build big-endian kernel"
561       help
562         Say Y if you plan on running a kernel in big-endian mode.
563
564config SCHED_MC
565	bool "Multi-core scheduler support"
566	help
567	  Multi-core scheduler support improves the CPU scheduler's decision
568	  making when dealing with multi-core CPU chips at a cost of slightly
569	  increased overhead in some places. If unsure say N here.
570
571config SCHED_SMT
572	bool "SMT scheduler support"
573	help
574	  Improves the CPU scheduler's decision making when dealing with
575	  MultiThreading at a cost of slightly increased overhead in some
576	  places. If unsure say N here.
577
578config NR_CPUS
579	int "Maximum number of CPUs (2-4096)"
580	range 2 4096
581	# These have to remain sorted largest to smallest
582	default "64"
583
584config HOTPLUG_CPU
585	bool "Support for hot-pluggable CPUs"
586	select GENERIC_IRQ_MIGRATION
587	help
588	  Say Y here to experiment with turning CPUs off and on.  CPUs
589	  can be controlled through /sys/devices/system/cpu.
590
591# Common NUMA Features
592config NUMA
593	bool "Numa Memory Allocation and Scheduler Support"
594	select ACPI_NUMA if ACPI
595	select OF_NUMA
596	help
597	  Enable NUMA (Non Uniform Memory Access) support.
598
599	  The kernel will try to allocate memory used by a CPU on the
600	  local memory of the CPU and add some more
601	  NUMA awareness to the kernel.
602
603config NODES_SHIFT
604	int "Maximum NUMA Nodes (as a power of 2)"
605	range 1 10
606	default "2"
607	depends on NEED_MULTIPLE_NODES
608	help
609	  Specify the maximum number of NUMA Nodes available on the target
610	  system.  Increases memory reserved to accommodate various tables.
611
612config USE_PERCPU_NUMA_NODE_ID
613	def_bool y
614	depends on NUMA
615
616config HAVE_SETUP_PER_CPU_AREA
617	def_bool y
618	depends on NUMA
619
620config NEED_PER_CPU_EMBED_FIRST_CHUNK
621	def_bool y
622	depends on NUMA
623
624source kernel/Kconfig.preempt
625source kernel/Kconfig.hz
626
627config ARCH_SUPPORTS_DEBUG_PAGEALLOC
628	def_bool y
629
630config ARCH_HAS_HOLES_MEMORYMODEL
631	def_bool y if SPARSEMEM
632
633config ARCH_SPARSEMEM_ENABLE
634	def_bool y
635	select SPARSEMEM_VMEMMAP_ENABLE
636
637config ARCH_SPARSEMEM_DEFAULT
638	def_bool ARCH_SPARSEMEM_ENABLE
639
640config ARCH_SELECT_MEMORY_MODEL
641	def_bool ARCH_SPARSEMEM_ENABLE
642
643config HAVE_ARCH_PFN_VALID
644	def_bool ARCH_HAS_HOLES_MEMORYMODEL || !SPARSEMEM
645
646config HW_PERF_EVENTS
647	def_bool y
648	depends on ARM_PMU
649
650config SYS_SUPPORTS_HUGETLBFS
651	def_bool y
652
653config ARCH_WANT_HUGE_PMD_SHARE
654	def_bool y if ARM64_4K_PAGES || (ARM64_16K_PAGES && !ARM64_VA_BITS_36)
655
656config ARCH_HAS_CACHE_LINE_SIZE
657	def_bool y
658
659source "mm/Kconfig"
660
661config SECCOMP
662	bool "Enable seccomp to safely compute untrusted bytecode"
663	---help---
664	  This kernel feature is useful for number crunching applications
665	  that may need to compute untrusted bytecode during their
666	  execution. By using pipes or other transports made available to
667	  the process as file descriptors supporting the read/write
668	  syscalls, it's possible to isolate those applications in
669	  their own address space using seccomp. Once seccomp is
670	  enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
671	  and the task is only allowed to execute a few safe syscalls
672	  defined by each seccomp mode.
673
674config PARAVIRT
675	bool "Enable paravirtualization code"
676	help
677	  This changes the kernel so it can modify itself when it is run
678	  under a hypervisor, potentially improving performance significantly
679	  over full virtualization.
680
681config PARAVIRT_TIME_ACCOUNTING
682	bool "Paravirtual steal time accounting"
683	select PARAVIRT
684	default n
685	help
686	  Select this option to enable fine granularity task steal time
687	  accounting. Time spent executing other tasks in parallel with
688	  the current vCPU is discounted from the vCPU power. To account for
689	  that, there can be a small performance impact.
690
691	  If in doubt, say N here.
692
693config KEXEC
694	depends on PM_SLEEP_SMP
695	select KEXEC_CORE
696	bool "kexec system call"
697	---help---
698	  kexec is a system call that implements the ability to shutdown your
699	  current kernel, and to start another kernel.  It is like a reboot
700	  but it is independent of the system firmware.   And like a reboot
701	  you can start any kernel with it, not just Linux.
702
703config XEN_DOM0
704	def_bool y
705	depends on XEN
706
707config XEN
708	bool "Xen guest support on ARM64"
709	depends on ARM64 && OF
710	select SWIOTLB_XEN
711	select PARAVIRT
712	help
713	  Say Y if you want to run Linux in a Virtual Machine on Xen on ARM64.
714
715config FORCE_MAX_ZONEORDER
716	int
717	default "14" if (ARM64_64K_PAGES && TRANSPARENT_HUGEPAGE)
718	default "12" if (ARM64_16K_PAGES && TRANSPARENT_HUGEPAGE)
719	default "11"
720	help
721	  The kernel memory allocator divides physically contiguous memory
722	  blocks into "zones", where each zone is a power of two number of
723	  pages.  This option selects the largest power of two that the kernel
724	  keeps in the memory allocator.  If you need to allocate very large
725	  blocks of physically contiguous memory, then you may need to
726	  increase this value.
727
728	  This config option is actually maximum order plus one. For example,
729	  a value of 11 means that the largest free memory block is 2^10 pages.
730
731	  We make sure that we can allocate upto a HugePage size for each configuration.
732	  Hence we have :
733		MAX_ORDER = (PMD_SHIFT - PAGE_SHIFT) + 1 => PAGE_SHIFT - 2
734
735	  However for 4K, we choose a higher default value, 11 as opposed to 10, giving us
736	  4M allocations matching the default size used by generic code.
737
738config UNMAP_KERNEL_AT_EL0
739	bool "Unmap kernel when running in userspace (aka \"KAISER\")" if EXPERT
740	default y
741	help
742	  Speculation attacks against some high-performance processors can
743	  be used to bypass MMU permission checks and leak kernel data to
744	  userspace. This can be defended against by unmapping the kernel
745	  when running in userspace, mapping it back in on exception entry
746	  via a trampoline page in the vector table.
747
748	  If unsure, say Y.
749
750config HARDEN_BRANCH_PREDICTOR
751	bool "Harden the branch predictor against aliasing attacks" if EXPERT
752	default y
753	help
754	  Speculation attacks against some high-performance processors rely on
755	  being able to manipulate the branch predictor for a victim context by
756	  executing aliasing branches in the attacker context.  Such attacks
757	  can be partially mitigated against by clearing internal branch
758	  predictor state and limiting the prediction logic in some situations.
759
760	  This config option will take CPU-specific actions to harden the
761	  branch predictor against aliasing attacks and may rely on specific
762	  instruction sequences or control bits being set by the system
763	  firmware.
764
765	  If unsure, say Y.
766
767menuconfig ARMV8_DEPRECATED
768	bool "Emulate deprecated/obsolete ARMv8 instructions"
769	depends on COMPAT
770	help
771	  Legacy software support may require certain instructions
772	  that have been deprecated or obsoleted in the architecture.
773
774	  Enable this config to enable selective emulation of these
775	  features.
776
777	  If unsure, say Y
778
779if ARMV8_DEPRECATED
780
781config SWP_EMULATION
782	bool "Emulate SWP/SWPB instructions"
783	help
784	  ARMv8 obsoletes the use of A32 SWP/SWPB instructions such that
785	  they are always undefined. Say Y here to enable software
786	  emulation of these instructions for userspace using LDXR/STXR.
787
788	  In some older versions of glibc [<=2.8] SWP is used during futex
789	  trylock() operations with the assumption that the code will not
790	  be preempted. This invalid assumption may be more likely to fail
791	  with SWP emulation enabled, leading to deadlock of the user
792	  application.
793
794	  NOTE: when accessing uncached shared regions, LDXR/STXR rely
795	  on an external transaction monitoring block called a global
796	  monitor to maintain update atomicity. If your system does not
797	  implement a global monitor, this option can cause programs that
798	  perform SWP operations to uncached memory to deadlock.
799
800	  If unsure, say Y
801
802config CP15_BARRIER_EMULATION
803	bool "Emulate CP15 Barrier instructions"
804	help
805	  The CP15 barrier instructions - CP15ISB, CP15DSB, and
806	  CP15DMB - are deprecated in ARMv8 (and ARMv7). It is
807	  strongly recommended to use the ISB, DSB, and DMB
808	  instructions instead.
809
810	  Say Y here to enable software emulation of these
811	  instructions for AArch32 userspace code. When this option is
812	  enabled, CP15 barrier usage is traced which can help
813	  identify software that needs updating.
814
815	  If unsure, say Y
816
817config SETEND_EMULATION
818	bool "Emulate SETEND instruction"
819	help
820	  The SETEND instruction alters the data-endianness of the
821	  AArch32 EL0, and is deprecated in ARMv8.
822
823	  Say Y here to enable software emulation of the instruction
824	  for AArch32 userspace code.
825
826	  Note: All the cpus on the system must have mixed endian support at EL0
827	  for this feature to be enabled. If a new CPU - which doesn't support mixed
828	  endian - is hotplugged in after this feature has been enabled, there could
829	  be unexpected results in the applications.
830
831	  If unsure, say Y
832endif
833
834config ARM64_SW_TTBR0_PAN
835	bool "Emulate Privileged Access Never using TTBR0_EL1 switching"
836	help
837	  Enabling this option prevents the kernel from accessing
838	  user-space memory directly by pointing TTBR0_EL1 to a reserved
839	  zeroed area and reserved ASID. The user access routines
840	  restore the valid TTBR0_EL1 temporarily.
841
842menu "ARMv8.1 architectural features"
843
844config ARM64_HW_AFDBM
845	bool "Support for hardware updates of the Access and Dirty page flags"
846	default y
847	help
848	  The ARMv8.1 architecture extensions introduce support for
849	  hardware updates of the access and dirty information in page
850	  table entries. When enabled in TCR_EL1 (HA and HD bits) on
851	  capable processors, accesses to pages with PTE_AF cleared will
852	  set this bit instead of raising an access flag fault.
853	  Similarly, writes to read-only pages with the DBM bit set will
854	  clear the read-only bit (AP[2]) instead of raising a
855	  permission fault.
856
857	  Kernels built with this configuration option enabled continue
858	  to work on pre-ARMv8.1 hardware and the performance impact is
859	  minimal. If unsure, say Y.
860
861config ARM64_PAN
862	bool "Enable support for Privileged Access Never (PAN)"
863	default y
864	help
865	 Privileged Access Never (PAN; part of the ARMv8.1 Extensions)
866	 prevents the kernel or hypervisor from accessing user-space (EL0)
867	 memory directly.
868
869	 Choosing this option will cause any unprotected (not using
870	 copy_to_user et al) memory access to fail with a permission fault.
871
872	 The feature is detected at runtime, and will remain as a 'nop'
873	 instruction if the cpu does not implement the feature.
874
875config ARM64_LSE_ATOMICS
876	bool "Atomic instructions"
877	help
878	  As part of the Large System Extensions, ARMv8.1 introduces new
879	  atomic instructions that are designed specifically to scale in
880	  very large systems.
881
882	  Say Y here to make use of these instructions for the in-kernel
883	  atomic routines. This incurs a small overhead on CPUs that do
884	  not support these instructions and requires the kernel to be
885	  built with binutils >= 2.25.
886
887config ARM64_VHE
888	bool "Enable support for Virtualization Host Extensions (VHE)"
889	default y
890	help
891	  Virtualization Host Extensions (VHE) allow the kernel to run
892	  directly at EL2 (instead of EL1) on processors that support
893	  it. This leads to better performance for KVM, as they reduce
894	  the cost of the world switch.
895
896	  Selecting this option allows the VHE feature to be detected
897	  at runtime, and does not affect processors that do not
898	  implement this feature.
899
900endmenu
901
902menu "ARMv8.2 architectural features"
903
904config ARM64_UAO
905	bool "Enable support for User Access Override (UAO)"
906	default y
907	help
908	  User Access Override (UAO; part of the ARMv8.2 Extensions)
909	  causes the 'unprivileged' variant of the load/store instructions to
910	  be overriden to be privileged.
911
912	  This option changes get_user() and friends to use the 'unprivileged'
913	  variant of the load/store instructions. This ensures that user-space
914	  really did have access to the supplied memory. When addr_limit is
915	  set to kernel memory the UAO bit will be set, allowing privileged
916	  access to kernel memory.
917
918	  Choosing this option will cause copy_to_user() et al to use user-space
919	  memory permissions.
920
921	  The feature is detected at runtime, the kernel will use the
922	  regular load/store instructions if the cpu does not implement the
923	  feature.
924
925endmenu
926
927config ARM64_MODULE_CMODEL_LARGE
928	bool
929
930config ARM64_MODULE_PLTS
931	bool
932	select ARM64_MODULE_CMODEL_LARGE
933	select HAVE_MOD_ARCH_SPECIFIC
934
935config RELOCATABLE
936	bool
937	help
938	  This builds the kernel as a Position Independent Executable (PIE),
939	  which retains all relocation metadata required to relocate the
940	  kernel binary at runtime to a different virtual address than the
941	  address it was linked at.
942	  Since AArch64 uses the RELA relocation format, this requires a
943	  relocation pass at runtime even if the kernel is loaded at the
944	  same address it was linked at.
945
946config RANDOMIZE_BASE
947	bool "Randomize the address of the kernel image"
948	select ARM64_MODULE_PLTS if MODULES
949	select RELOCATABLE
950	help
951	  Randomizes the virtual address at which the kernel image is
952	  loaded, as a security feature that deters exploit attempts
953	  relying on knowledge of the location of kernel internals.
954
955	  It is the bootloader's job to provide entropy, by passing a
956	  random u64 value in /chosen/kaslr-seed at kernel entry.
957
958	  When booting via the UEFI stub, it will invoke the firmware's
959	  EFI_RNG_PROTOCOL implementation (if available) to supply entropy
960	  to the kernel proper. In addition, it will randomise the physical
961	  location of the kernel Image as well.
962
963	  If unsure, say N.
964
965config RANDOMIZE_MODULE_REGION_FULL
966	bool "Randomize the module region independently from the core kernel"
967	depends on RANDOMIZE_BASE && !DYNAMIC_FTRACE && !LTO_CLANG
968	default y
969	help
970	  Randomizes the location of the module region without considering the
971	  location of the core kernel. This way, it is impossible for modules
972	  to leak information about the location of core kernel data structures
973	  but it does imply that function calls between modules and the core
974	  kernel will need to be resolved via veneers in the module PLT.
975
976	  When this option is not set, the module region will be randomized over
977	  a limited range that contains the [_stext, _etext] interval of the
978	  core kernel, so branch relocations are always in range.
979
980endmenu
981
982menu "Boot options"
983
984config ARM64_ACPI_PARKING_PROTOCOL
985	bool "Enable support for the ARM64 ACPI parking protocol"
986	depends on ACPI
987	help
988	  Enable support for the ARM64 ACPI parking protocol. If disabled
989	  the kernel will not allow booting through the ARM64 ACPI parking
990	  protocol even if the corresponding data is present in the ACPI
991	  MADT table.
992
993config CMDLINE
994	string "Default kernel command string"
995	default ""
996	help
997	  Provide a set of default command-line options at build time by
998	  entering them here. As a minimum, you should specify the the
999	  root device (e.g. root=/dev/nfs).
1000
1001choice
1002	prompt "Kernel command line type" if CMDLINE != ""
1003	default CMDLINE_FROM_BOOTLOADER
1004
1005config CMDLINE_FROM_BOOTLOADER
1006	bool "Use bootloader kernel arguments if available"
1007	help
1008	  Uses the command-line options passed by the boot loader. If
1009	  the boot loader doesn't provide any, the default kernel command
1010	  string provided in CMDLINE will be used.
1011
1012config CMDLINE_EXTEND
1013	bool "Extend bootloader kernel arguments"
1014	help
1015	  The command-line arguments provided by the boot loader will be
1016	  appended to the default kernel command string.
1017
1018config CMDLINE_FORCE
1019	bool "Always use the default kernel command string"
1020	help
1021	  Always use the default kernel command string, even if the boot
1022	  loader passes other arguments to the kernel.
1023	  This is useful if you cannot or don't want to change the
1024	  command-line options your boot loader passes to the kernel.
1025endchoice
1026
1027config EFI_STUB
1028	bool
1029
1030config EFI
1031	bool "UEFI runtime support"
1032	depends on OF && !CPU_BIG_ENDIAN
1033	select LIBFDT
1034	select UCS2_STRING
1035	select EFI_PARAMS_FROM_FDT
1036	select EFI_RUNTIME_WRAPPERS
1037	select EFI_STUB
1038	select EFI_ARMSTUB
1039	default y
1040	help
1041	  This option provides support for runtime services provided
1042	  by UEFI firmware (such as non-volatile variables, realtime
1043          clock, and platform reset). A UEFI stub is also provided to
1044	  allow the kernel to be booted as an EFI application. This
1045	  is only useful on systems that have UEFI firmware.
1046
1047config DMI
1048	bool "Enable support for SMBIOS (DMI) tables"
1049	depends on EFI
1050	default y
1051	help
1052	  This enables SMBIOS/DMI feature for systems.
1053
1054	  This option is only useful on systems that have UEFI firmware.
1055	  However, even with this option, the resultant kernel should
1056	  continue to boot on existing non-UEFI platforms.
1057
1058config BUILD_ARM64_APPENDED_DTB_IMAGE
1059	bool "Build a concatenated Image.gz/dtb by default"
1060	depends on OF
1061	help
1062	  Enabling this option will cause a concatenated Image.gz and list of
1063	  DTBs to be built by default (instead of a standalone Image.gz.)
1064	  The image will built in arch/arm64/boot/Image.gz-dtb
1065
1066choice
1067	prompt "Appended DTB Kernel Image name"
1068	depends on BUILD_ARM64_APPENDED_DTB_IMAGE
1069	help
1070	  Enabling this option will cause a specific kernel image Image or
1071	  Image.gz to be used for final image creation.
1072	  The image will built in arch/arm64/boot/IMAGE-NAME-dtb
1073
1074	config IMG_GZ_DTB
1075		bool "Image.gz-dtb"
1076	config IMG_DTB
1077		bool "Image-dtb"
1078endchoice
1079
1080config BUILD_ARM64_APPENDED_KERNEL_IMAGE_NAME
1081	string
1082	depends on BUILD_ARM64_APPENDED_DTB_IMAGE
1083	default "Image.gz-dtb" if IMG_GZ_DTB
1084	default "Image-dtb" if IMG_DTB
1085
1086config BUILD_ARM64_APPENDED_DTB_IMAGE_NAMES
1087	string "Default dtb names"
1088	depends on BUILD_ARM64_APPENDED_DTB_IMAGE
1089	help
1090	  Space separated list of names of dtbs to append when
1091	  building a concatenated Image.gz-dtb.
1092
1093endmenu
1094
1095menu "Userspace binary formats"
1096
1097source "fs/Kconfig.binfmt"
1098
1099config COMPAT
1100	bool "Kernel support for 32-bit EL0"
1101	depends on ARM64_4K_PAGES || EXPERT
1102	select COMPAT_BINFMT_ELF if BINFMT_ELF
1103	select HAVE_UID16
1104	select OLD_SIGSUSPEND3
1105	select COMPAT_OLD_SIGACTION
1106	help
1107	  This option enables support for a 32-bit EL0 running under a 64-bit
1108	  kernel at EL1. AArch32-specific components such as system calls,
1109	  the user helper functions, VFP support and the ptrace interface are
1110	  handled appropriately by the kernel.
1111
1112	  If you use a page size other than 4KB (i.e, 16KB or 64KB), please be aware
1113	  that you will only be able to execute AArch32 binaries that were compiled
1114	  with page size aligned segments.
1115
1116	  If you want to execute 32-bit userspace applications, say Y.
1117
1118config SYSVIPC_COMPAT
1119	def_bool y
1120	depends on COMPAT && SYSVIPC
1121
1122endmenu
1123
1124menu "Power management options"
1125
1126source "kernel/power/Kconfig"
1127
1128config ARCH_HIBERNATION_POSSIBLE
1129	def_bool y
1130	depends on CPU_PM
1131
1132config ARCH_HIBERNATION_HEADER
1133	def_bool y
1134	depends on HIBERNATION
1135
1136config ARCH_SUSPEND_POSSIBLE
1137	def_bool y
1138
1139endmenu
1140
1141menu "CPU Power Management"
1142
1143source "drivers/cpuidle/Kconfig"
1144
1145source "drivers/cpufreq/Kconfig"
1146
1147endmenu
1148
1149source "net/Kconfig"
1150
1151source "drivers/Kconfig"
1152
1153source "drivers/firmware/Kconfig"
1154
1155source "drivers/acpi/Kconfig"
1156
1157source "fs/Kconfig"
1158
1159source "arch/arm64/kvm/Kconfig"
1160
1161source "arch/arm64/Kconfig.debug"
1162
1163source "security/Kconfig"
1164
1165source "crypto/Kconfig"
1166if CRYPTO
1167source "arch/arm64/crypto/Kconfig"
1168endif
1169
1170source "lib/Kconfig"
1171