Changes in Makefile

1684e829 - arm/crc-t10dif: expose CRC-T10DIF function through lib

Mon, 02 Dec 2024 01:20:49 +0000

arm/crc-t10dif: expose CRC-T10DIF function through libMove the arm CRC-T10DIF assembly code into the lib directory and wire itup to the library interface. This allows it to be used without goingthrough the crypto API. It remains usable via the crypto API too viathe shash algorithms that use the library interface. Thus all thearch-specific "shash" code becomes unnecessary and is removed.Note: to see the diff from arch/arm/crypto/crct10dif-ce-glue.c toarch/arm/lib/crc-t10dif-glue.c, view this commit with 'git show -M10'.Reviewed-by: Ard Biesheuvel Reviewed-by: Martin K. Petersen Link: https://lore.kernel.org/r/20241202012056.209768-6-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux-6.15/arch/arm/lib/Makefile

1e1b6dbc - arm/crc32: expose CRC32 functions through lib

Mon, 02 Dec 2024 01:08:30 +0000

arm/crc32: expose CRC32 functions through libMove the arm CRC32 assembly code into the lib directory and wire it upto the library interface. This allows it to be used without goingthrough the crypto API. It remains usable via the crypto API too viathe shash algorithms that use the library interface. Thus all thearch-specific "shash" code becomes unnecessary and is removed.Note: to see the diff from arch/arm/crypto/crc32-ce-glue.c toarch/arm/lib/crc32-glue.c, view this commit with 'git show -M10'.Reviewed-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20241202010844.144356-6-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux-6.15/arch/arm/lib/Makefile

c4162431 - ARM: crypto: use CC_FLAGS_FPU for NEON CFLAGS

Fri, 29 Mar 2024 07:18:18 +0000

ARM: crypto: use CC_FLAGS_FPU for NEON CFLAGSNow that CC_FLAGS_FPU is exported and can be used anywhere in the sourcetree, use it instead of duplicating the flags here.Link: https://lkml.kernel.org/r/20240329072441.591471-4-samuel.holland@sifive.comSigned-off-by: Samuel Holland Reviewed-by: Christoph Hellwig Acked-by: Christian König Cc: Alex Deucher Cc: Borislav Petkov (AMD) Cc: Catalin Marinas Cc: Dave Hansen Cc: Huacai Chen Cc: Ingo Molnar Cc: Jonathan Corbet Cc: Masahiro Yamada Cc: Michael Ellerman Cc: Nathan Chancellor Cc: Nicolas Schier Cc: Palmer Dabbelt Cc: Russell King Cc: Thomas Gleixner Cc: WANG Xuerui Cc: Will Deacon Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/arm/lib/Makefile

aaa4dd1b - ARM: 9279/1: support function error injection

Sun, 04 Dec 2022 03:46:40 +0000

ARM: 9279/1: support function error injectionThis enables HAVE_FUNCTION_ERROR_INJECTION by adding necessaryregs_set_return_value() and override_function_with_return().Simply tested according to Documentation/fault-injection/fault-injection.rst.Signed-off-by: Kefeng Wang Signed-off-by: Russell King (Oracle) List of files: /linux-6.15/arch/arm/lib/Makefile

a2faac39 - ARM: 9263/1: use .arch directives instead of assembler command line flags

Mon, 24 Oct 2022 19:44:41 +0000

ARM: 9263/1: use .arch directives instead of assembler command line flagsSimilar to commit a6c30873ee4a ("ARM: 8989/1: use .fpu assemblerdirectives instead of assembler arguments").GCC and GNU binutils support setting the "sub arch" via -march=,-Wa,-march, target function attribute, and .arch assembler directive.Clang was missing support for -Wa,-march=, but this was implemented inclang-13.The behavior of both GCC and Clang is toprefer -Wa,-march= over -march= for assembler and assembler-with-cppsources, but Clang will warn about the -march= being unused.clang: warning: argument unused during compilation: '-march=armv6k'[-Wunused-command-line-argument]Since most assembler is non-conditionally assembled with one sub arch(modulo arch/arm/delay-loop.S which conditionally is assembled as armv4based on CONFIG_ARCH_RPC, and arch/arm/mach-at91/pm-suspend.S which isconditionally assembled as armv7-a based on CONFIG_CPU_V7), prefer the.arch assembler directive.Add a few more instances found in compile testing as found by Arnd andNathan.Link: https://github.com/llvm/llvm-project/commit/1d51c699b9e2ebc5bcfdbe85c74cc871426333d4Link: https://bugs.llvm.org/show_bug.cgi?id=48894Link: https://github.com/ClangBuiltLinux/linux/issues/1195Link: https://github.com/ClangBuiltLinux/linux/issues/1315Suggested-by: Arnd Bergmann Suggested-by: Nathan Chancellor Signed-off-by: Arnd Bergmann Tested-by: Nathan Chancellor Signed-off-by: Nick Desaulniers Signed-off-by: Russell King (Oracle) List of files: /linux-6.15/arch/arm/lib/Makefile

6dc5fd93 - ARM: 8900/1: UNWINDER_FRAME_POINTER implementation for Clang

Thu, 22 Aug 2019 20:26:53 +0000

ARM: 8900/1: UNWINDER_FRAME_POINTER implementation for ClangThe stackframe setup when compiled with clang is different.Since the stack unwinder expects the gcc stackframe setup itfails to print backtraces. This patch adds support for theclang stackframe setup.Link: https://github.com/ClangBuiltLinux/linux/issues/35Cc: clang-built-linux@googlegroups.comSuggested-by: Tri Vo Signed-off-by: Nathan Huckleberry Tested-by: Nick Desaulniers Reviewed-by: Nick Desaulniers Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

12290cc4 - ARM: riscpc: move RiscPC assembly files from arch/arm/lib to mach-rpc

Tue, 21 May 2019 14:31:42 +0000

ARM: riscpc: move RiscPC assembly files from arch/arm/lib to mach-rpcMove the assembly files for RiscPC from arch/arm/lib to mach-rpc sothat we contain RiscPC bits in one subdirectory.Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

de9c0d49 - ARM: 8833/1: Ensure that NEON code always compiles with Clang

Sat, 02 Feb 2019 02:34:36 +0000

ARM: 8833/1: Ensure that NEON code always compiles with ClangWhile building arm32 allyesconfig, I ran into the following errors: arch/arm/lib/xor-neon.c:17:2: error: You should compile this file with '-mfloat-abi=softfp -mfpu=neon' In file included from lib/raid6/neon1.c:27: /home/nathan/cbl/prebuilt/lib/clang/8.0.0/include/arm_neon.h:28:2: error: "NEON support not enabled"Building V=1 showed NEON_FLAGS getting passed along to Clang but__ARM_NEON__ was not getting defined. Ultimately, it boils down to Clangonly defining __ARM_NEON__ when targeting armv7, rather than armv6k,which is the '-march' value for allyesconfig.>From lib/Basic/Targets/ARM.cpp in the Clang source: // This only gets set when Neon instructions are actually available, unlike // the VFP define, hence the soft float and arch check. This is subtly // different from gcc, we follow the intent which was that it should be set // when Neon instructions are actually available. if ((FPU & NeonFPU) && !SoftFloat && ArchVersion >= 7) { Builder.defineMacro("__ARM_NEON", "1"); Builder.defineMacro("__ARM_NEON__"); // current AArch32 NEON implementations do not support double-precision // floating-point even when it is present in VFP. Builder.defineMacro("__ARM_NEON_FP", "0x" + Twine::utohexstr(HW_FP & ~HW_FP_DP)); }Ard Biesheuvel recommended explicitly adding '-march=armv7-a' at thebeginning of the NEON_FLAGS definitions so that __ARM_NEON__ always getsdefinined by Clang. This doesn't functionally change anything becausethat code will only run where NEON is supported, which is implicitlyarmv7.Link: https://github.com/ClangBuiltLinux/linux/issues/287Suggested-by: Ard Biesheuvel Signed-off-by: Nathan Chancellor Acked-by: Nicolas Pitre Reviewed-by: Nick Desaulniers Reviewed-by: Stefan Agner Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

ff5fdafc - ARM: 8745/1: get rid of __memzero()

Fri, 19 Jan 2018 17:17:46 +0000

ARM: 8745/1: get rid of __memzero()The __memzero assembly code is almost identical to memset's except fortwo orr instructions. The runtime performance of __memset(p, n) andmemset(p, 0, n) is accordingly almost identical.However, the memset() macro used to guard against a zero length and tocall __memzero at compile time when the fill value is a constant zerointerferes with compiler optimizations.Arnd found tha the test against a zero length brings up some newwarnings with gcc v8: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82103And successively rremoving the test against a zero length and the callto __memzero optimization produces the following kernel sizes fordefconfig with gcc 6: text data bss dec hex filename12248142 6278960 413588 18940690 1210312 vmlinux.orig12244474 6278960 413588 18937022 120f4be vmlinux.no_zero_test12239160 6278960 413588 18931708 120dffc vmlinux.no_memzeroSo it is probably not worth keeping __memzero around given that thecompiler can do a better job at inlining trivial memset(p,0,n) on itsown. And the memset code already handles a zero length just fine.Suggested-by: Arnd Bergmann Signed-off-by: Nicolas Pitre Acked-by: Ard Biesheuvel Acked-by: Arnd Bergmann Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/arch/arm/lib/Makefile

215e362d - ARM: 8306/1: loop_udelay: remove bogomips value limitation

Wed, 25 Feb 2015 21:50:39 +0000

ARM: 8306/1: loop_udelay: remove bogomips value limitationNow that we don't support ARMv3 anymore, the loop based delay code canconvert microsecs into number of loops using a 64-bit multiplicationand more precision.This allows us to lift the hard limit of 3355 on the bogomips value asloops_per_jiffy may now safely span the full 32-bit range.Signed-off-by: Nicolas Pitre Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

c2563038 - ARM: 8285/1: remove ARMv3 user access code again

Thu, 15 Jan 2015 22:41:54 +0000

ARM: 8285/1: remove ARMv3 user access code againThis code was restored with commit 080fc66fb5 ("ARM: Bring back ARMv3 IOand user access code") because the RiscPC memory bus does not understandhalf-word load/stores. However only the IO code needed restoring sincethe alternative user access code contains no half-word accesses, isalready used when CONFIG_PREEMPT is set and runs faster on a StrongARM.Signed-off-by: Nicolas Pitre Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

017f161a - ARM: 7877/1: use built-in byte swap function

Wed, 06 Nov 2013 04:15:24 +0000

ARM: 7877/1: use built-in byte swap functionEnable the compiler intrinsic for byte swapping on arch ARM. Thisallows the compiler to detect and be able to optimize out byteswappings, and has a very modest benefit on vmlinux size (Linaro gcc4.8):text data bss dec hex filename2840310 123932 61960 3026202 2e2d1a vmlinux-lart #orig2840152 123932 61960 3026044 2e2c7c vmlinux-lart #builtin-bswap6473120 314840 5616016 12403976 bd4508 vmlinux-mxs #orig6472586 314848 5616016 12403450 bd42fa vmlinux-mxs #builtin-bswap7419872 318372 379556 8117800 7bde28 vmlinux-imx_v6_v7 #orig7419170 318364 379556 8117090 7bdb62 vmlinux-imx_v6_v7 #builtin-bswapSigned-off-by: Kim Phillips Reviewed-by: Nicolas Pitre Acked-by: David Woodhouse Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

136dfa5e - ARM: delete mach-shark

Tue, 03 Sep 2013 09:32:24 +0000

ARM: delete mach-sharkThe Shark machine sub-architecture (also known as DNARD, theDIGITAL Network Appliance Reference Design) lacks a maintainerable to apply and test patches to modernize the architecture.It is suspected that the current kernel, while it compiles,does not even boot on this machine. The listed maintainer hasexpressed that he will not be able to spend any time on themaintenance for the coming year.So let's delete it from the kernel for now. It can always beresurrected with git revert if maintenance is resumed.As the VIA82c505 PCI adapter was only used by thisarchitecture, that gets deleted too.Cc: arm@kernel.orgCc: Alexander Schulz Signed-off-by: Linus Walleij List of files: /linux-6.15/arch/arm/lib/Makefile

9319206d - ARM: 7835/2: fix modular build of xor_blocks() with NEON enabled

Mon, 09 Sep 2013 14:08:38 +0000

ARM: 7835/2: fix modular build of xor_blocks() with NEON enabledCommit 0195659 introduced a NEON accelerated version of the xor_blocks()function, but it needs the changes in this patch to allow it to be builtas a module rather than statically into the kernel.This patch creates a separate module xor-neon.ko which exports the NEONinner xor_blocks() functions depended upon by the regular xor.ko if itis built with CONFIG_KERNEL_MODE_NEON=yReported-by: Josh Boyer Signed-off-by: Ard Biesheuvel Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

01956597 - ARM: crypto: add NEON accelerated XOR implementation

Fri, 17 May 2013 16:51:23 +0000

ARM: crypto: add NEON accelerated XOR implementationAdd a source file xor-neon.c (which is really just the referenceC implementation passed through the GCC vectorizer) and hook itup to the XOR framework.Signed-off-by: Ard Biesheuvel Acked-by: Nicolas Pitre List of files: /linux-6.15/arch/arm/lib/Makefile

080fc66f - ARM: Bring back ARMv3 IO and user access code

Mon, 13 Aug 2012 10:44:13 +0000

ARM: Bring back ARMv3 IO and user access codeThis partially reverts 357c9c1f07d4546bc3fbc0fd1044d96b114d14ed(ARM: Remove support for ARMv3 ARM610 and ARM710 CPUs).Although we only support StrongARM on the RiscPC, we need to keep theARMv3 user access code for this platform because the bus does notunderstand half-word load/stores.Reported-by: Arnd Bergmann Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

d0a533b1 - ARM: 7452/1: delay: allow timer-based delay implementation to be selected

Fri, 06 Jul 2012 14:47:17 +0000

ARM: 7452/1: delay: allow timer-based delay implementation to be selectedThis patch allows a timer-based delay implementation to be selected byswitching the delay routines over to use get_cycles, which isimplemented in terms of read_current_timer. This further allows us toskip the loop calibration and have a consistent delay function in theface of core frequency scaling.To avoid the pain of dealing with memory-mapped counters, thisimplementation uses the co-processor interface to the architected timerswhen they are available. The previous loop-based implementation iskept around for CPUs without the architected timers and we retain boththe maximum delay (2ms) and the corresponding conversion factors fordetermining the number of loops required for a given interval. Since theindirection of the timer routines will only work when called from C,the sa1100 sleep routines are modified to branch to the loop-based delayfunctions directly.Tested-by: Shinya Kuribayashi Reviewed-by: Stephen Boyd Signed-off-by: Will Deacon Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

8c56cc8b - ARM: 7449/1: use generic strnlen_user and strncpy_from_user functions

Fri, 06 Jul 2012 14:45:39 +0000

ARM: 7449/1: use generic strnlen_user and strncpy_from_user functionsThis patch implements the word-at-a-time interface for ARM using thesame algorithm as x86. We use the fls macro from ARMv5 onwards, wherewe have a clz instruction available which saves us a mov instructionwhen targetting Thumb-2. For older CPUs, we use the magic 0x0ff0001constant. Big-endian configurations make use of the implementation fromasm-generic.With this implemented, we can replace our byte-at-a-time strnlen_userand strncpy_from_user functions with the optimised generic versions.Reviewed-by: Nicolas Pitre Signed-off-by: Will Deacon Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile

357c9c1f - ARM: Remove support for ARMv3 ARM610 and ARM710 CPUs

Fri, 04 May 2012 11:04:26 +0000

ARM: Remove support for ARMv3 ARM610 and ARM710 CPUsThis patch removes support for ARMv3 CPUs, which haven't worked properlyfor quite some time (see the FIXME comment in arch/arm/mm/fault.c). Theonly V3 parts left is the cache model for ARMv3, which is needed for someodd reason by ARM740T CPUs, and being able to build with -march=armv3,which is required for the RiscPC platform due to its bus structure.Acked-by: Will Deacon Acked-by: Jean-Christophe PLAGNIOL-VILLARD Signed-off-by: Russell King List of files: /linux-6.15/arch/arm/lib/Makefile