1 comment "Processor Type"
3 # Select CPU types depending on the architecture selected. This selects
4 # which CPUs we support in the kernel image, and the compiler instruction
14 select CPU_PABRT_LEGACY
16 A 32-bit RISC microprocessor based on the ARM7 processor core
17 which has no memory control unit and cache.
19 Say Y if you want support for the ARM7TDMI processor.
29 select CPU_COPY_V4WT if MMU
31 select CPU_PABRT_LEGACY
32 select CPU_TLB_V4WT if MMU
34 A 32-bit RISC processor with 8kByte Cache, Write Buffer and
35 MMU built around an ARM7TDMI core.
37 Say Y if you want support for the ARM720T processor.
48 select CPU_PABRT_LEGACY
50 A 32-bit RISC processor with 8KB cache or 4KB variants,
51 write buffer and MPU(Protection Unit) built around
54 Say Y if you want support for the ARM740T processor.
64 select CPU_PABRT_LEGACY
66 A 32-bit RISC microprocessor based on the ARM9 processor core
67 which has no memory control unit and cache.
69 Say Y if you want support for the ARM9TDMI processor.
79 select CPU_COPY_V4WB if MMU
81 select CPU_PABRT_LEGACY
82 select CPU_TLB_V4WBI if MMU
84 The ARM920T is licensed to be produced by numerous vendors,
85 and is used in the Cirrus EP93xx and the Samsung S3C2410.
87 Say Y if you want support for the ARM920T processor.
97 select CPU_COPY_V4WB if MMU
99 select CPU_PABRT_LEGACY
100 select CPU_TLB_V4WBI if MMU
102 The ARM922T is a version of the ARM920T, but with smaller
103 instruction and data caches. It is used in Altera's
104 Excalibur XA device family and Micrel's KS8695 Centaur.
106 Say Y if you want support for the ARM922T processor.
114 select CPU_CACHE_V4WT
115 select CPU_CACHE_VIVT
116 select CPU_COPY_V4WB if MMU
118 select CPU_PABRT_LEGACY
119 select CPU_TLB_V4WBI if MMU
121 The ARM925T is a mix between the ARM920T and ARM926T, but with
122 different instruction and data caches. It is used in TI's OMAP
125 Say Y if you want support for the ARM925T processor.
132 select CPU_ABRT_EV5TJ
133 select CPU_CACHE_VIVT
134 select CPU_COPY_V4WB if MMU
136 select CPU_PABRT_LEGACY
137 select CPU_TLB_V4WBI if MMU
139 This is a variant of the ARM920. It has slightly different
140 instruction sequences for cache and TLB operations. Curiously,
141 there is no documentation on it at the ARM corporate website.
143 Say Y if you want support for the ARM926T processor.
152 select CPU_CACHE_VIVT
153 select CPU_COPY_FA if MMU
155 select CPU_PABRT_LEGACY
156 select CPU_TLB_FA if MMU
158 The FA526 is a version of the ARMv4 compatible processor with
159 Branch Target Buffer, Unified TLB and cache line size 16.
161 Say Y if you want support for the FA526 processor.
169 select CPU_ABRT_NOMMU
170 select CPU_CACHE_VIVT
172 select CPU_PABRT_LEGACY
174 ARM940T is a member of the ARM9TDMI family of general-
175 purpose microprocessors with MPU and separate 4KB
176 instruction and 4KB data cases, each with a 4-word line
179 Say Y if you want support for the ARM940T processor.
187 select CPU_ABRT_NOMMU
188 select CPU_CACHE_VIVT
190 select CPU_PABRT_LEGACY
192 ARM946E-S is a member of the ARM9E-S family of high-
193 performance, 32-bit system-on-chip processor solutions.
194 The TCM and ARMv5TE 32-bit instruction set is supported.
196 Say Y if you want support for the ARM946E-S processor.
199 # ARM1020 - needs validating
204 select CPU_CACHE_V4WT
205 select CPU_CACHE_VIVT
206 select CPU_COPY_V4WB if MMU
208 select CPU_PABRT_LEGACY
209 select CPU_TLB_V4WBI if MMU
211 The ARM1020 is the 32K cached version of the ARM10 processor,
212 with an addition of a floating-point unit.
214 Say Y if you want support for the ARM1020 processor.
217 # ARM1020E - needs validating
223 select CPU_CACHE_V4WT
224 select CPU_CACHE_VIVT
225 select CPU_COPY_V4WB if MMU
227 select CPU_PABRT_LEGACY
228 select CPU_TLB_V4WBI if MMU
235 select CPU_CACHE_VIVT
236 select CPU_COPY_V4WB if MMU # can probably do better
238 select CPU_PABRT_LEGACY
239 select CPU_TLB_V4WBI if MMU
241 The ARM1022E is an implementation of the ARMv5TE architecture
242 based upon the ARM10 integer core with a 16KiB L1 Harvard cache,
243 embedded trace macrocell, and a floating-point unit.
245 Say Y if you want support for the ARM1022E processor.
252 select CPU_ABRT_EV5T # But need Jazelle, but EV5TJ ignores bit 10
253 select CPU_CACHE_VIVT
254 select CPU_COPY_V4WB if MMU # can probably do better
256 select CPU_PABRT_LEGACY
257 select CPU_TLB_V4WBI if MMU
259 The ARM1026EJ-S is an implementation of the ARMv5TEJ architecture
260 based upon the ARM10 integer core.
262 Say Y if you want support for the ARM1026EJ-S processor.
268 select CPU_32v3 if ARCH_RPC
269 select CPU_32v4 if !ARCH_RPC
271 select CPU_CACHE_V4WB
272 select CPU_CACHE_VIVT
273 select CPU_COPY_V4WB if MMU
275 select CPU_PABRT_LEGACY
276 select CPU_TLB_V4WB if MMU
278 The Intel StrongARM(R) SA-110 is a 32-bit microprocessor and
279 is available at five speeds ranging from 100 MHz to 233 MHz.
280 More information is available at
281 <http://developer.intel.com/design/strong/sa110.htm>.
283 Say Y if you want support for the SA-110 processor.
291 select CPU_CACHE_V4WB
292 select CPU_CACHE_VIVT
294 select CPU_PABRT_LEGACY
295 select CPU_TLB_V4WB if MMU
302 select CPU_CACHE_VIVT
304 select CPU_PABRT_LEGACY
305 select CPU_TLB_V4WBI if MMU
307 # XScale Core Version 3
312 select CPU_CACHE_VIVT
314 select CPU_PABRT_LEGACY
315 select CPU_TLB_V4WBI if MMU
318 # Marvell PJ1 (Mohawk)
323 select CPU_CACHE_VIVT
324 select CPU_COPY_V4WB if MMU
326 select CPU_PABRT_LEGACY
327 select CPU_TLB_V4WBI if MMU
334 select CPU_CACHE_VIVT
335 select CPU_COPY_FEROCEON if MMU
337 select CPU_PABRT_LEGACY
338 select CPU_TLB_FEROCEON if MMU
340 config CPU_FEROCEON_OLD_ID
341 bool "Accept early Feroceon cores with an ARM926 ID"
342 depends on CPU_FEROCEON && !CPU_ARM926T
345 This enables the usage of some old Feroceon cores
346 for which the CPU ID is equal to the ARM926 ID.
347 Relevant for Feroceon-1850 and early Feroceon-2850.
365 select CPU_CACHE_VIPT
366 select CPU_COPY_V6 if MMU
368 select CPU_HAS_ASID if MMU
370 select CPU_TLB_V6 if MMU
379 select CPU_CACHE_VIPT
380 select CPU_COPY_V6 if MMU
382 select CPU_HAS_ASID if MMU
384 select CPU_TLB_V6 if MMU
393 select CPU_CACHE_VIPT
394 select CPU_COPY_V6 if MMU
395 select CPU_CP15_MMU if MMU
396 select CPU_CP15_MPU if !MMU
397 select CPU_HAS_ASID if MMU
399 select CPU_SPECTRE if MMU
400 select CPU_TLB_V7 if MMU
406 select CPU_ABRT_NOMMU
409 select CPU_PABRT_LEGACY
414 # There are no CPUs available with MMU that don't implement an ARM ISA:
417 Select this if your CPU doesn't support the 32 bit ARM instructions.
419 # Figure out what processor architecture version we should be using.
420 # This defines the compiler instruction set which depends on the machine type.
423 select CPU_USE_DOMAINS if MMU
424 select NEED_KUSER_HELPERS
425 select TLS_REG_EMUL if SMP || !MMU
426 select CPU_NO_EFFICIENT_FFS
430 select CPU_USE_DOMAINS if MMU
431 select NEED_KUSER_HELPERS
432 select TLS_REG_EMUL if SMP || !MMU
433 select CPU_NO_EFFICIENT_FFS
437 select CPU_USE_DOMAINS if MMU
438 select NEED_KUSER_HELPERS
439 select TLS_REG_EMUL if SMP || !MMU
440 select CPU_NO_EFFICIENT_FFS
444 select CPU_USE_DOMAINS if MMU
445 select NEED_KUSER_HELPERS
446 select TLS_REG_EMUL if SMP || !MMU
450 select TLS_REG_EMUL if !CPU_32v6K && !MMU
462 config CPU_ABRT_NOMMU
477 config CPU_ABRT_EV5TJ
486 config CPU_PABRT_LEGACY
499 config CPU_CACHE_V4WT
502 config CPU_CACHE_V4WB
514 config CPU_CACHE_VIVT
517 config CPU_CACHE_VIPT
527 # The copy-page model
534 config CPU_COPY_FEROCEON
543 # This selects the TLB model
547 ARM Architecture Version 4 TLB with writethrough cache.
552 ARM Architecture Version 4 TLB with writeback cache.
557 ARM Architecture Version 4 TLB with writeback cache and invalidate
558 instruction cache entry.
560 config CPU_TLB_FEROCEON
563 Feroceon TLB (v4wbi with non-outer-cachable page table walks).
568 Faraday ARM FA526 architecture, unified TLB with writeback cache
569 and invalidate instruction cache entry. Branch target buffer is
578 config VERIFY_PERMISSION_FAULT
585 This indicates whether the CPU has the ASID register; used to
586 tag TLB and possibly cache entries.
591 Processor has the CP15 register.
597 Processor has the CP15 register, which has MMU related registers.
603 Processor has the CP15 register, which has MPU related registers.
605 config CPU_USE_DOMAINS
608 This option enables or disables the use of domain switching
609 via the set_fs() function.
611 config CPU_V7M_NUM_IRQ
612 int "Number of external interrupts connected to the NVIC"
614 default 90 if ARCH_STM32
615 default 38 if ARCH_EFM32
616 default 112 if SOC_VF610
619 This option indicates the number of interrupts connected to the NVIC.
620 The value can be larger than the real number of interrupts supported
621 by the system, but must not be lower.
622 The default value is 240, corresponding to the maximum number of
623 interrupts supported by the NVIC on Cortex-M family.
625 If unsure, keep default value.
628 # CPU supports 36-bit I/O
633 comment "Processor Features"
636 bool "Support for the Large Physical Address Extension"
637 depends on MMU && CPU_32v7 && !CPU_32v6 && !CPU_32v5 && \
638 !CPU_32v4 && !CPU_32v3
640 Say Y if you have an ARMv7 processor supporting the LPAE page
641 table format and you would like to access memory beyond the
642 4GB limit. The resulting kernel image will not run on
643 processors without the LPA extension.
649 depends on ARM_LPAE && ARM_PATCH_PHYS_VIRT && ARCH_KEYSTONE
651 config ARCH_PHYS_ADDR_T_64BIT
654 config ARCH_DMA_ADDR_T_64BIT
658 bool "Support Thumb user binaries" if !CPU_THUMBONLY
659 depends on CPU_ARM720T || CPU_ARM740T || CPU_ARM920T || CPU_ARM922T || \
660 CPU_ARM925T || CPU_ARM926T || CPU_ARM940T || CPU_ARM946E || \
661 CPU_ARM1020 || CPU_ARM1020E || CPU_ARM1022 || CPU_ARM1026 || \
662 CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_V6 || CPU_V6K || \
663 CPU_V7 || CPU_FEROCEON || CPU_V7M
666 Say Y if you want to include kernel support for running user space
669 The Thumb instruction set is a compressed form of the standard ARM
670 instruction set resulting in smaller binaries at the expense of
671 slightly less efficient code.
673 If you don't know what this all is, saying Y is a safe choice.
676 bool "Enable ThumbEE CPU extension"
679 Say Y here if you have a CPU with the ThumbEE extension and code to
680 make use of it. Say N for code that can run on CPUs without ThumbEE.
687 Enable the kernel to make use of the ARM Virtualization
688 Extensions to install hypervisors without run-time firmware
691 A compliant bootloader is required in order to make maximum
692 use of this feature. Refer to Documentation/arm/Booting for
696 bool "Emulate SWP/SWPB instructions" if !SMP
699 select HAVE_PROC_CPU if PROC_FS
701 ARMv6 architecture deprecates use of the SWP/SWPB instructions.
702 ARMv7 multiprocessing extensions introduce the ability to disable
703 these instructions, triggering an undefined instruction exception
704 when executed. Say Y here to enable software emulation of these
705 instructions for userspace (not kernel) using LDREX/STREX.
706 Also creates /proc/cpu/swp_emulation for statistics.
708 In some older versions of glibc [<=2.8] SWP is used during futex
709 trylock() operations with the assumption that the code will not
710 be preempted. This invalid assumption may be more likely to fail
711 with SWP emulation enabled, leading to deadlock of the user
714 NOTE: when accessing uncached shared regions, LDREX/STREX rely
715 on an external transaction monitoring block called a global
716 monitor to maintain update atomicity. If your system does not
717 implement a global monitor, this option can cause programs that
718 perform SWP operations to uncached memory to deadlock.
722 config CPU_BIG_ENDIAN
723 bool "Build big-endian kernel"
724 depends on ARCH_SUPPORTS_BIG_ENDIAN
726 Say Y if you plan on running a kernel in big-endian mode.
727 Note that your board must be properly built and your board
728 port must properly enable any big-endian related features
729 of your chipset/board/processor.
731 config CPU_ENDIAN_BE8
733 depends on CPU_BIG_ENDIAN
734 default CPU_V6 || CPU_V6K || CPU_V7 || CPU_V7M
736 Support for the BE-8 (big-endian) mode on ARMv6 and ARMv7 processors.
738 config CPU_ENDIAN_BE32
740 depends on CPU_BIG_ENDIAN
741 default !CPU_ENDIAN_BE8
743 Support for the BE-32 (big-endian) mode on pre-ARMv6 processors.
745 config CPU_HIGH_VECTOR
746 depends on !MMU && CPU_CP15 && !CPU_ARM740T
747 bool "Select the High exception vector"
749 Say Y here to select high exception vector(0xFFFF0000~).
750 The exception vector can vary depending on the platform
751 design in nommu mode. If your platform needs to select
752 high exception vector, say Y.
753 Otherwise or if you are unsure, say N, and the low exception
754 vector (0x00000000~) will be used.
756 config CPU_ICACHE_DISABLE
757 bool "Disable I-Cache (I-bit)"
758 depends on (CPU_CP15 && !(CPU_ARM720T || CPU_ARM740T || CPU_XSCALE || CPU_XSC3)) || CPU_V7M
760 Say Y here to disable the processor instruction cache. Unless
761 you have a reason not to or are unsure, say N.
763 config CPU_DCACHE_DISABLE
764 bool "Disable D-Cache (C-bit)"
765 depends on (CPU_CP15 && !SMP) || CPU_V7M
767 Say Y here to disable the processor data cache. Unless
768 you have a reason not to or are unsure, say N.
770 config CPU_DCACHE_SIZE
772 depends on CPU_ARM740T || CPU_ARM946E
773 default 0x00001000 if CPU_ARM740T
774 default 0x00002000 # default size for ARM946E-S
776 Some cores are synthesizable to have various sized cache. For
777 ARM946E-S case, it can vary from 0KB to 1MB.
778 To support such cache operations, it is efficient to know the size
780 If your SoC is configured to have a different size, define the value
781 here with proper conditions.
783 config CPU_DCACHE_WRITETHROUGH
784 bool "Force write through D-cache"
785 depends on (CPU_ARM740T || CPU_ARM920T || CPU_ARM922T || CPU_ARM925T || CPU_ARM926T || CPU_ARM940T || CPU_ARM946E || CPU_ARM1020 || CPU_FA526) && !CPU_DCACHE_DISABLE
786 default y if CPU_ARM925T
788 Say Y here to use the data cache in writethrough mode. Unless you
789 specifically require this or are unsure, say N.
791 config CPU_CACHE_ROUND_ROBIN
792 bool "Round robin I and D cache replacement algorithm"
793 depends on (CPU_ARM926T || CPU_ARM946E || CPU_ARM1020) && (!CPU_ICACHE_DISABLE || !CPU_DCACHE_DISABLE)
795 Say Y here to use the predictable round-robin cache replacement
796 policy. Unless you specifically require this or are unsure, say N.
798 config CPU_BPREDICT_DISABLE
799 bool "Disable branch prediction"
800 depends on CPU_ARM1020 || CPU_V6 || CPU_V6K || CPU_MOHAWK || CPU_XSC3 || CPU_V7 || CPU_FA526 || CPU_V7M
802 Say Y here to disable branch prediction. If unsure, say N.
806 select GENERIC_CPU_VULNERABILITIES
808 config HARDEN_BRANCH_PREDICTOR
809 bool "Harden the branch predictor against aliasing attacks" if EXPERT
810 depends on CPU_SPECTRE
813 Speculation attacks against some high-performance processors rely
814 on being able to manipulate the branch predictor for a victim
815 context by executing aliasing branches in the attacker context.
816 Such attacks can be partially mitigated against by clearing
817 internal branch predictor state and limiting the prediction
818 logic in some situations.
820 This config option will take CPU-specific actions to harden
821 the branch predictor against aliasing attacks and may rely on
822 specific instruction sequences or control bits being set by
827 config HARDEN_BRANCH_HISTORY
828 bool "Harden Spectre style attacks against branch history" if EXPERT
829 depends on CPU_SPECTRE
832 Speculation attacks against some high-performance processors can
833 make use of branch history to influence future speculation. When
834 taking an exception, a sequence of branches overwrites the branch
835 history, or branch history is invalidated.
839 select NEED_KUSER_HELPERS
841 An SMP system using a pre-ARMv6 processor (there are apparently
842 a few prototypes like that in existence) and therefore access to
843 that required register must be emulated.
845 config NEED_KUSER_HELPERS
849 bool "Enable kuser helpers in vector page" if !NEED_KUSER_HELPERS
853 Warning: disabling this option may break user programs.
855 Provide kuser helpers in the vector page. The kernel provides
856 helper code to userspace in read only form at a fixed location
857 in the high vector page to allow userspace to be independent of
858 the CPU type fitted to the system. This permits binaries to be
859 run on ARMv4 through to ARMv7 without modification.
861 See Documentation/arm/kernel_user_helpers.txt for details.
863 However, the fixed address nature of these helpers can be used
864 by ROP (return orientated programming) authors when creating
867 If all of the binaries and libraries which run on your platform
868 are built specifically for your platform, and make no use of
869 these helpers, then you can turn this option off to hinder
870 such exploits. However, in that case, if a binary or library
871 relying on those helpers is run, it will receive a SIGILL signal,
872 which will terminate the program.
874 Say N here only if you are absolutely certain that you do not
875 need these helpers; otherwise, the safe option is to say Y.
878 bool "Enable VDSO for acceleration of some system calls"
879 depends on AEABI && MMU && CPU_V7
880 default y if ARM_ARCH_TIMER
881 select GENERIC_TIME_VSYSCALL
883 Place in the process address space an ELF shared object
884 providing fast implementations of gettimeofday and
885 clock_gettime. Systems that implement the ARM architected
886 timer will receive maximum benefit.
888 You must have glibc 2.22 or later for programs to seamlessly
889 take advantage of this.
891 config DMA_CACHE_RWFO
892 bool "Enable read/write for ownership DMA cache maintenance"
893 depends on CPU_V6K && SMP
896 The Snoop Control Unit on ARM11MPCore does not detect the
897 cache maintenance operations and the dma_{map,unmap}_area()
898 functions may leave stale cache entries on other CPUs. By
899 enabling this option, Read or Write For Ownership in the ARMv6
900 DMA cache maintenance functions is performed. These LDR/STR
901 instructions change the cache line state to shared or modified
902 so that the cache operation has the desired effect.
904 Note that the workaround is only valid on processors that do
905 not perform speculative loads into the D-cache. For such
906 processors, if cache maintenance operations are not broadcast
907 in hardware, other workarounds are needed (e.g. cache
908 maintenance broadcasting in software via FIQ).
913 config OUTER_CACHE_SYNC
917 The outer cache has a outer_cache_fns.sync function pointer
918 that can be used to drain the write buffer of the outer cache.
920 config CACHE_FEROCEON_L2
921 bool "Enable the Feroceon L2 cache controller"
922 depends on ARCH_MV78XX0 || ARCH_MVEBU
926 This option enables the Feroceon L2 cache controller.
928 config CACHE_FEROCEON_L2_WRITETHROUGH
929 bool "Force Feroceon L2 cache write through"
930 depends on CACHE_FEROCEON_L2
932 Say Y here to use the Feroceon L2 cache in writethrough mode.
933 Unless you specifically require this, say N for writeback mode.
935 config MIGHT_HAVE_CACHE_L2X0
938 This option should be selected by machines which have a L2x0
939 or PL310 cache controller, but where its use is optional.
941 The only effect of this option is to make CACHE_L2X0 and
942 related options available to the user for configuration.
944 Boards or SoCs which always require the cache controller
945 support to be present should select CACHE_L2X0 directly
946 instead of this option, thus preventing the user from
947 inadvertently configuring a broken kernel.
950 bool "Enable the L2x0 outer cache controller" if MIGHT_HAVE_CACHE_L2X0
951 default MIGHT_HAVE_CACHE_L2X0
953 select OUTER_CACHE_SYNC
955 This option enables the L2x0 PrimeCell.
957 config CACHE_L2X0_PMU
958 bool "L2x0 performance monitor support" if CACHE_L2X0
959 depends on PERF_EVENTS
961 This option enables support for the performance monitoring features
962 of the L220 and PL310 outer cache controllers.
966 config PL310_ERRATA_588369
967 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
969 The PL310 L2 cache controller implements three types of Clean &
970 Invalidate maintenance operations: by Physical Address
971 (offset 0x7F0), by Index/Way (0x7F8) and by Way (0x7FC).
972 They are architecturally defined to behave as the execution of a
973 clean operation followed immediately by an invalidate operation,
974 both performing to the same memory location. This functionality
975 is not correctly implemented in PL310 prior to r2p0 (fixed in r2p0)
976 as clean lines are not invalidated as a result of these operations.
978 config PL310_ERRATA_727915
979 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
981 PL310 implements the Clean & Invalidate by Way L2 cache maintenance
982 operation (offset 0x7FC). This operation runs in background so that
983 PL310 can handle normal accesses while it is in progress. Under very
984 rare circumstances, due to this erratum, write data can be lost when
985 PL310 treats a cacheable write transaction during a Clean &
986 Invalidate by Way operation. Revisions prior to r3p1 are affected by
987 this errata (fixed in r3p1).
989 config PL310_ERRATA_753970
990 bool "PL310 errata: cache sync operation may be faulty"
992 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
994 Under some condition the effect of cache sync operation on
995 the store buffer still remains when the operation completes.
996 This means that the store buffer is always asked to drain and
997 this prevents it from merging any further writes. The workaround
998 is to replace the normal offset of cache sync operation (0x730)
999 by another offset targeting an unmapped PL310 register 0x740.
1000 This has the same effect as the cache sync operation: store buffer
1001 drain and waiting for all buffers empty.
1003 config PL310_ERRATA_769419
1004 bool "PL310 errata: no automatic Store Buffer drain"
1006 On revisions of the PL310 prior to r3p2, the Store Buffer does
1007 not automatically drain. This can cause normal, non-cacheable
1008 writes to be retained when the memory system is idle, leading
1009 to suboptimal I/O performance for drivers using coherent DMA.
1010 This option adds a write barrier to the cpu_idle loop so that,
1011 on systems with an outer cache, the store buffer is drained
1016 config CACHE_TAUROS2
1017 bool "Enable the Tauros2 L2 cache controller"
1018 depends on (ARCH_DOVE || ARCH_MMP || CPU_PJ4)
1022 This option enables the Tauros2 L2 cache controller (as
1025 config CACHE_UNIPHIER
1026 bool "Enable the UniPhier outer cache controller"
1027 depends on ARCH_UNIPHIER
1030 select OUTER_CACHE_SYNC
1032 This option enables the UniPhier outer cache (system cache)
1036 bool "Enable the L2 cache on XScale3"
1041 This option enables the L2 cache on XScale3.
1043 config ARM_L1_CACHE_SHIFT_6
1047 Setting ARM L1 cache line size to 64 Bytes.
1049 config ARM_L1_CACHE_SHIFT
1051 default 6 if ARM_L1_CACHE_SHIFT_6
1054 config ARM_DMA_MEM_BUFFERABLE
1055 bool "Use non-cacheable memory for DMA" if (CPU_V6 || CPU_V6K) && !CPU_V7
1056 default y if CPU_V6 || CPU_V6K || CPU_V7
1058 Historically, the kernel has used strongly ordered mappings to
1059 provide DMA coherent memory. With the advent of ARMv7, mapping
1060 memory with differing types results in unpredictable behaviour,
1061 so on these CPUs, this option is forced on.
1063 Multiple mappings with differing attributes is also unpredictable
1064 on ARMv6 CPUs, but since they do not have aggressive speculative
1065 prefetch, no harm appears to occur.
1067 However, drivers may be missing the necessary barriers for ARMv6,
1068 and therefore turning this on may result in unpredictable driver
1069 behaviour. Therefore, we offer this as an option.
1071 You are recommended say 'Y' here and debug any affected drivers.
1076 config ARCH_SUPPORTS_BIG_ENDIAN
1079 This option specifies the architecture can support big endian
1083 bool "Make kernel text and rodata read-only"
1084 depends on MMU && !XIP_KERNEL
1087 If this is set, kernel text and rodata memory will be made
1088 read-only, and non-text kernel memory will be made non-executable.
1089 The tradeoff is that each region is padded to section-size (1MiB)
1090 boundaries (because their permissions are different and splitting
1091 the 1M pages into 4K ones causes TLB performance problems), which
1094 config DEBUG_ALIGN_RODATA
1095 bool "Make rodata strictly non-executable"
1096 depends on DEBUG_RODATA
1099 If this is set, rodata will be made explicitly non-executable. This
1100 provides protection on the rare chance that attackers might find and
1101 use ROP gadgets that exist in the rodata section. This adds an
1102 additional section-aligned split of rodata from kernel text so it
1103 can be made explicitly non-executable. This padding may waste memory
1104 space to gain the additional protection.