Changes in Makefile

54ac9ff8f1196afc49d644a1625e0af1c9fcf7f5 - arm64: Use static call trampolines when kCFI is enabled

Tue, 31 Mar 2026 13:04:23 +0200

arm64: Use static call trampolines when kCFI is enabledImplement arm64 support for the 'unoptimized' static call variety, whichroutes all calls through a trampoline that performs a tail call to thechosen function, and wire it up for use when kCFI is enabled. This worksaround an issue with kCFI and generic static calls, where the prototypesof default handlers such as __static_call_nop() and __static_call_ret0()don't match the expected prototype of the call site, resulting in kCFIfalse positives [0].Since static call targets may be located in modules loaded out of directbranching range, this needs an ADRP/LDR pair to load the branch targetinto R16 and a branch-to-register (BR) instruction to perform anindirect call.Unlike on x86, there is no pressing need on arm64 to avoid indirectcalls at all cost, but hiding it from the compiler as is done here doeshave some benefits:- the literal is located in .rodata, which gives us the same robustness advantage that code patching does;- no D-cache pollution from fetching hash values from .text sections.From an execution speed PoV, this is unlikely to make any difference atall.Cc: Sami Tolvanen Cc: Sean Christopherson Cc: Kees Cook Cc: Peter Zijlstra Cc: Will McVicker Reported-by: Carlos Llamas Closes: https://lore.kernel.org/all/20260311225822.1565895-1-cmllamas@google.com/ [0]Signed-off-by: Ard Biesheuvel Signed-off-by: Will Deacon Signed-off-by: Catalin Marinas List of files: /linux/arch/arm64/kernel/Makefile

6fb44438a5e1897a72dd11139274735256be8069 - Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux

Wed, 30 Jul 2025 05:21:54 +0200

Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linuxPull arm64 updates from Catalin Marinas: "A quick summary: perf support for Branch Record Buffer Extensions (BRBE), typical PMU hardware updates, small additions to MTE for store-only tag checking and exposing non-address bits to signal handlers, HAVE_LIVEPATCH enabled on arm64, VMAP_STACK forced on. There is also a TLBI optimisation on hardware that does not require break-before-make when changing the user PTEs between contiguous and non-contiguous. More details: Perf and PMU updates: - Add support for new (v3) Hisilicon SLLC and DDRC PMUs - Add support for Arm-NI PMU integrations that share interrupts between clock domains within a given instance - Allow SPE to be configured with a lower sample period than the minimum recommendation advertised by PMSIDR_EL1.Interval - Add suppport for Arm's "Branch Record Buffer Extension" (BRBE) - Adjust the perf watchdog period according to cpu frequency changes - Minor driver fixes and cleanups Hardware features: - Support for MTE store-only checking (FEAT_MTE_STORE_ONLY) - Support for reporting the non-address bits during a synchronous MTE tag check fault (FEAT_MTE_TAGGED_FAR) - Optimise the TLBI when folding/unfolding contiguous PTEs on hardware with FEAT_BBM (break-before-make) level 2 and no TLB conflict aborts Software features: - Enable HAVE_LIVEPATCH after implementing arch_stack_walk_reliable() and using the text-poke API for late module relocations - Force VMAP_STACK always on and change arm64_efi_rt_init() to use arch_alloc_vmap_stack() in order to avoid KASAN false positives ACPI: - Improve SPCR handling and messaging on systems lacking an SPCR table Debug: - Simplify the debug exception entry path - Drop redundant DBG_MDSCR_* macros Kselftests: - Cleanups and improvements for SME, SVE and FPSIMD tests Miscellaneous: - Optimise loop to reduce redundant operations in contpte_ptep_get() - Remove ISB when resetting POR_EL0 during signal handling - Mark the kernel as tainted on SEA and SError panic - Remove redundant gcs_free() call"* tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux: (93 commits) arm64/gcs: task_gcs_el0_enable() should use passed task arm64: Kconfig: Keep selects somewhat alphabetically ordered arm64: signal: Remove ISB when resetting POR_EL0 kselftest/arm64: Handle attempts to disable SM on SME only systems kselftest/arm64: Fix SVE write data generation for SME only systems kselftest/arm64: Test SME on SME only systems in fp-ptrace kselftest/arm64: Test FPSIMD format data writes via NT_ARM_SVE in fp-ptrace kselftest/arm64: Allow sve-ptrace to run on SME only systems arm64/mm: Drop redundant addr increment in set_huge_pte_at() kselftest/arm4: Provide local defines for AT_HWCAP3 arm64: Mark kernel as tainted on SAE and SError panic arm64/gcs: Don't call gcs_free() when releasing task_struct drivers/perf: hisi: Support PMUs with no interrupt drivers/perf: hisi: Relax the event number check of v2 PMUs drivers/perf: hisi: Add support for HiSilicon SLLC v3 PMU driver drivers/perf: hisi: Use ACPI driver_data to retrieve SLLC PMU information drivers/perf: hisi: Add support for HiSilicon DDRC v3 PMU driver drivers/perf: hisi: Simplify the probe process for each DDRC version perf/arm-ni: Support sharing IRQs within an NI instance perf/arm-ni: Consolidate CPU affinity handling ... List of files: /linux/arch/arm64/kernel/Makefile

344b6580472451390d070c65c27f59716a1deecb - arm64: fix unnecessary rebuilding when CONFIG_DEBUG_EFI=y

Wed, 25 Jun 2025 14:55:20 +0200

arm64: fix unnecessary rebuilding when CONFIG_DEBUG_EFI=yWhen CONFIG_DEBUG_EFI is enabled, some objects are needlessly rebuilt.[Steps to reproduce] Enable CONFIG_DEBUG_EFI and run 'make' twice in a clean source tree. On the second run, arch/arm64/kernel/head.o is rebuilt even though no files have changed. $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- clean $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- [ snip ] $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- CALL scripts/checksyscalls.sh AS arch/arm64/kernel/head.o AR arch/arm64/kernel/built-in.a AR arch/arm64/built-in.a AR built-in.a [ snip ]The issue is caused by the use of the $(realpath ...) function.At the time arch/arm64/kernel/Makefile is parsed on the first run,$(objtree)/vmlinux does not exist. As a result,$(realpath $(objtree)/vmlinux) expands to an empty string.On the second run of Make, $(objtree)/vmlinux already exists, so$(realpath $(objtree)/vmlinux) expands to the absolute path of vmlinux.However, this change in the command line causes arch/arm64/kernel/head.oto be rebuilt.To address this issue, use $(abspath ...) instead, which does not requirethe file to exist. While $(abspath ...) does not resolve symlinks, thisshould be fine from a debugging perspective.The GNU Make manual [1] clearly explains the difference between the two: $(realpath names...) For each file name in names return the canonical absolute name. A canonical name does not contain any . or .. components, nor any repeated path separators (/) or symlinks. In case of a failure the empty string is returned. Consult the realpath(3) documentation for a list of possible failure causes. $(abspath namees...) For each file name in names return an absolute name that does not contain any . or .. components, nor any repeated path separators (/). Note that, in contrast to realpath function, abspath does not resolve symlinks and does not require the file names to refer to an existing file or directory. Use the wildcard function to test for existence.The same problem exists in drivers/firmware/efi/libstub/Makefile.zboot.On the first run of Make, $(obj)/vmlinuz.efi.elf does not exist when theMakefile is parsed, so -DZBOOT_EFI_PATH is set to an empty string.Replace $(realpath ...) with $(abspath ...) there as well.[1]: https://www.gnu.org/software/make/manual/make.html#File-Name-FunctionsFixes: 757b435aaabe ("efi: arm64: Add vmlinux debug link to the Image binary")Fixes: a050910972bb ("efi/libstub: implement generic EFI zboot")Signed-off-by: Masahiro Yamada Acked-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20250625125555.2504734-1-masahiroy@kernel.orgSigned-off-by: Will Deacon List of files: /linux/arch/arm64/kernel/Makefile

727c2a53cf959f599493c50a80fe2a356b8b1df6 - arm64: Unconditionally select CONFIG_JUMP_LABEL

Fri, 13 Jun 2025 16:19:36 +0200

arm64: Unconditionally select CONFIG_JUMP_LABELAneesh reports that his kernel fails to boot in nVHE mode withKVM's protected mode enabled. Further investigation by Mostafareveals that this fails because CONFIG_JUMP_LABEL=n and thatwe have static keys shared between EL1 and EL2.While this can be worked around, it is obvious that we have longrelied on having CONFIG_JUMP_LABEL enabled at all times, as allsupported compilers now have 'asm goto' (which is the basic blockfor jump labels).Let's simplify our lives once and for all by mandating jump labels.It's not like anyone else is testing anything without them, andwe already rely on them for other things (kfence, xfs, preempt).Link: https://lore.kernel.org/r/yq5ah60pkq03.fsf@kernel.orgReported-by: Aneesh Kumar K.V Reported-by: Mostafa Saleh Signed-off-by: Marc Zyngier Cc: Will Deacon Cc: Catalin marinas Cc: Mark Rutland Cc: Ard Biesheuvel Acked-by: Mark Rutland Link: https://lore.kernel.org/r/20250613141936.2219895-1-maz@kernel.orgSigned-off-by: Will Deacon List of files: /linux/arch/arm64/kernel/Makefile

e21efe833eae4e2a56c2c2a11caae870a65926fa - arch: use always-$(KBUILD_BUILTIN) for vmlinux.lds

Mon, 02 Jun 2025 20:12:54 +0200

arch: use always-$(KBUILD_BUILTIN) for vmlinux.ldsThe extra-y syntax is deprecated. Instead, use always-$(KBUILD_BUILTIN),which behaves equivalently.Signed-off-by: Masahiro Yamada Acked-by: Johannes Berg Reviewed-by: Nicolas Schier List of files: /linux/arch/arm64/kernel/Makefile

c077711f718be7cebcc8b987eac2ebfd17447e9f - arm64: Detect if in a realm and set RIPAS RAM

Thu, 17 Oct 2024 15:14:25 +0200

arm64: Detect if in a realm and set RIPAS RAMDetect that the VM is a realm guest by the presence of the RSIinterface. This is done after PSCI has been initialised so that we cancheck the SMCCC conduit before making any RSI calls.If in a realm then iterate over all memory ensuring that it is marked asRIPAS RAM. The loader is required to do this for us, however if somememory is missed this will cause the guest to receive a hard to debugexternal abort at some random point in the future. So for abelt-and-braces approach set all memory to RIPAS RAM. Any failure hereimplies that the RAM regions passed to Linux are incorrect so panic()promptly to make the situation clear.Reviewed-by: Gavin Shan Reviewed-by: Catalin Marinas Signed-off-by: Suzuki K Poulose Co-developed-by: Steven Price Signed-off-by: Steven Price Link: https://lore.kernel.org/r/20241017131434.40935-3-steven.price@arm.comSigned-off-by: Catalin Marinas List of files: /linux/arch/arm64/kernel/Makefile

99e7a8adc0ca906151f5d70ff68b8a81f53fd106 - arm64: cpuidle: Move ACPI specific code into drivers/acpi/arm64/

Wed, 05 Jun 2024 15:14:57 +0200

arm64: cpuidle: Move ACPI specific code into drivers/acpi/arm64/The ACPI cpuidle LPI FFH code can be moved out of arm64 arch code asit just uses SMCCC. Move all the ACPI cpuidle LPI FFH code intodrivers/acpi/arm64/cpuidle.cSigned-off-by: Sudeep Holla Acked-by: Catalin Marinas Acked-by: Hanjun Guo Link: https://lore.kernel.org/r/20240605131458.3341095-3-sudeep.holla@arm.comSigned-off-by: Catalin Marinas List of files: /linux/arch/arm64/kernel/Makefile

902861e34c401696ed9ad17a54c8790e7e8e3069 - Merge tag 'mm-stable-2024-03-13-20-04' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Fri, 15 Mar 2024 01:43:30 +0100

Merge tag 'mm-stable-2024-03-13-20-04' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mmPull MM updates from Andrew Morton: - Sumanth Korikkar has taught s390 to allocate hotplug-time page frames from hotplugged memory rather than only from main memory. Series "implement "memmap on memory" feature on s390". - More folio conversions from Matthew Wilcox in the series "Convert memcontrol charge moving to use folios" "mm: convert mm counter to take a folio" - Chengming Zhou has optimized zswap's rbtree locking, providing significant reductions in system time and modest but measurable reductions in overall runtimes. The series is "mm/zswap: optimize the scalability of zswap rb-tree". - Chengming Zhou has also provided the series "mm/zswap: optimize zswap lru list" which provides measurable runtime benefits in some swap-intensive situations. - And Chengming Zhou further optimizes zswap in the series "mm/zswap: optimize for dynamic zswap_pools". Measured improvements are modest. - zswap cleanups and simplifications from Yosry Ahmed in the series "mm: zswap: simplify zswap_swapoff()". - In the series "Add DAX ABI for memmap_on_memory", Vishal Verma has contributed several DAX cleanups as well as adding a sysfs tunable to control the memmap_on_memory setting when the dax device is hotplugged as system memory. - Johannes Weiner has added the large series "mm: zswap: cleanups", which does that. - More DAMON work from SeongJae Park in the series "mm/damon: make DAMON debugfs interface deprecation unignorable" "selftests/damon: add more tests for core functionalities and corner cases" "Docs/mm/damon: misc readability improvements" "mm/damon: let DAMOS feeds and tame/auto-tune itself" - In the series "mm/mempolicy: weighted interleave mempolicy and sysfs extension" Rakie Kim has developed a new mempolicy interleaving policy wherein we allocate memory across nodes in a weighted fashion rather than uniformly. This is beneficial in heterogeneous memory environments appearing with CXL. - Christophe Leroy has contributed some cleanup and consolidation work against the ARM pagetable dumping code in the series "mm: ptdump: Refactor CONFIG_DEBUG_WX and check_wx_pages debugfs attribute". - Luis Chamberlain has added some additional xarray selftesting in the series "test_xarray: advanced API multi-index tests". - Muhammad Usama Anjum has reworked the selftest code to make its human-readable output conform to the TAP ("Test Anything Protocol") format. Amongst other things, this opens up the use of third-party tools to parse and process out selftesting results. - Ryan Roberts has added fork()-time PTE batching of THP ptes in the series "mm/memory: optimize fork() with PTE-mapped THP". Mainly targeted at arm64, this significantly speeds up fork() when the process has a large number of pte-mapped folios. - David Hildenbrand also gets in on the THP pte batching game in his series "mm/memory: optimize unmap/zap with PTE-mapped THP". It implements batching during munmap() and other pte teardown situations. The microbenchmark improvements are nice. - And in the series "Transparent Contiguous PTEs for User Mappings" Ryan Roberts further utilizes arm's pte's contiguous bit ("contpte mappings"). Kernel build times on arm64 improved nicely. Ryan's series "Address some contpte nits" provides some followup work. - In the series "mm/hugetlb: Restore the reservation" Breno Leitao has fixed an obscure hugetlb race which was causing unnecessary page faults. He has also added a reproducer under the selftest code. - In the series "selftests/mm: Output cleanups for the compaction test", Mark Brown did what the title claims. - Kinsey Ho has added the series "mm/mglru: code cleanup and refactoring". - Even more zswap material from Nhat Pham. The series "fix and extend zswap kselftests" does as claimed. - In the series "Introduce cpu_dcache_is_aliasing() to fix DAX regression" Mathieu Desnoyers has cleaned up and fixed rather a mess in our handling of DAX on archiecctures which have virtually aliasing data caches. The arm architecture is the main beneficiary. - Lokesh Gidra's series "per-vma locks in userfaultfd" provides dramatic improvements in worst-case mmap_lock hold times during certain userfaultfd operations. - Some page_owner enhancements and maintenance work from Oscar Salvador in his series "page_owner: print stacks and their outstanding allocations" "page_owner: Fixup and cleanup" - Uladzislau Rezki has contributed some vmalloc scalability improvements in his series "Mitigate a vmap lock contention". It realizes a 12x improvement for a certain microbenchmark. - Some kexec/crash cleanup work from Baoquan He in the series "Split crash out from kexec and clean up related config items". - Some zsmalloc maintenance work from Chengming Zhou in the series "mm/zsmalloc: fix and optimize objects/page migration" "mm/zsmalloc: some cleanup for get/set_zspage_mapping()" - Zi Yan has taught the MM to perform compaction on folios larger than order=0. This a step along the path to implementaton of the merging of large anonymous folios. The series is named "Enable >0 order folio memory compaction". - Christoph Hellwig has done quite a lot of cleanup work in the pagecache writeback code in his series "convert write_cache_pages() to an iterator". - Some modest hugetlb cleanups and speedups in Vishal Moola's series "Handle hugetlb faults under the VMA lock". - Zi Yan has changed the page splitting code so we can split huge pages into sizes other than order-0 to better utilize large folios. The series is named "Split a folio to any lower order folios". - David Hildenbrand has contributed the series "mm: remove total_mapcount()", a cleanup. - Matthew Wilcox has sought to improve the performance of bulk memory freeing in his series "Rearrange batched folio freeing". - Gang Li's series "hugetlb: parallelize hugetlb page init on boot" provides large improvements in bootup times on large machines which are configured to use large numbers of hugetlb pages. - Matthew Wilcox's series "PageFlags cleanups" does that. - Qi Zheng's series "minor fixes and supplement for ptdesc" does that also. S390 is affected. - Cleanups to our pagemap utility functions from Peter Xu in his series "mm/treewide: Replace pXd_large() with pXd_leaf()". - Nico Pache has fixed a few things with our hugepage selftests in his series "selftests/mm: Improve Hugepage Test Handling in MM Selftests". - Also, of course, many singleton patches to many things. Please see the individual changelogs for details.* tag 'mm-stable-2024-03-13-20-04' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (435 commits) mm/zswap: remove the memcpy if acomp is not sleepable crypto: introduce: acomp_is_async to expose if comp drivers might sleep memtest: use {READ,WRITE}_ONCE in memory scanning mm: prohibit the last subpage from reusing the entire large folio mm: recover pud_leaf() definitions in nopmd case selftests/mm: skip the hugetlb-madvise tests on unmet hugepage requirements selftests/mm: skip uffd hugetlb tests with insufficient hugepages selftests/mm: dont fail testsuite due to a lack of hugepages mm/huge_memory: skip invalid debugfs new_order input for folio split mm/huge_memory: check new folio order when split a folio mm, vmscan: retry kswapd's priority loop with cache_trim_mode off on failure mm: add an explicit smp_wmb() to UFFDIO_CONTINUE mm: fix list corruption in put_pages_list mm: remove folio from deferred split list before uncharging it filemap: avoid unnecessary major faults in filemap_fault() mm,page_owner: drop unnecessary check mm,page_owner: check for null stack_record before bumping its refcount mm: swap: fix race between free_swap_and_cache() and swapoff() mm/treewide: align up pXd_leaf() retval across archs mm/treewide: drop pXd_large() ... List of files: /linux/arch/arm64/kernel/Makefile

443cbaf9e2fdbef7d7cae457434a6cb8a679441b - crash: split vmcoreinfo exporting code out from crash_core.c

Wed, 24 Jan 2024 06:12:42 +0100

crash: split vmcoreinfo exporting code out from crash_core.cNow move the relevant codes into separate files:kernel/crash_reserve.c, include/linux/crash_reserve.h.And add config item CRASH_RESERVE to control its enabling.And also update the old ifdeffery of CONFIG_CRASH_CORE, including of and config item dependency on CRASH_COREaccordingly.And also do renaming as follows: - arch/xxx/kernel/{crash_core.c => vmcore_info.c}because they are only related to vmcoreinfo exporting on x86, arm64,riscv.And also Remove config item CRASH_CORE, and rely on CONFIG_KEXEC_CORE todecide if build in crash_core.c.[yang.lee@linux.alibaba.com: remove duplicated include in vmcore_info.c] Link: https://lkml.kernel.org/r/20240126005744.16561-1-yang.lee@linux.alibaba.comLink: https://lkml.kernel.org/r/20240124051254.67105-3-bhe@redhat.comSigned-off-by: Baoquan He Signed-off-by: Yang Li Acked-by: Hari Bathini Cc: Al Viro Cc: Eric W. Biederman Cc: Pingfan Liu Cc: Klara Modin Cc: Michael Kelley Cc: Nathan Chancellor Cc: Stephen Rothwell Cc: Yang Li Signed-off-by: Andrew Morton List of files: /linux/arch/arm64/kernel/Makefile

8a6e40e1f68e9fc44497db88e0c0f21bb513c551 - arm64: head: move dynamic shadow call stack patching into early C runtime

Wed, 14 Feb 2024 13:28:55 +0100

arm64: head: move dynamic shadow call stack patching into early C runtimeOnce we update the early kernel mapping code to only map the kernel oncewith the right permissions, we can no longer perform code patching viathis mapping.So move this code to an earlier stage of the boot, right after applyingthe relocations.Signed-off-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20240214122845.2033971-54-ardb+git@google.comSigned-off-by: Catalin Marinas List of files: /linux/arch/arm64/kernel/Makefile

e223a449125571daa62debd8249fa4fc2da0a961 - arm64: idreg-override: Move to early mini C runtime

Wed, 14 Feb 2024 13:28:50 +0100

arm64: idreg-override: Move to early mini C runtimeWe will want to parse the ID register overrides even earlier, so that wecan take them into account before creating the kernel mapping. Somigrate the code and make it work in the context of the early C runtime.We will move the invocation to an earlier stage in a subsequent patch.Signed-off-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20240214122845.2033971-49-ardb+git@google.comSigned-off-by: Catalin Marinas List of files: /linux/arch/arm64/kernel/Makefile

734958ef0b5497b1b9cb827afb541e7825477bbd - arm64: head: move relocation handling to C code

Wed, 14 Feb 2024 13:28:49 +0100

arm64: head: move relocation handling to C codeNow that we have a mini C runtime before the kernel mapping is up, wecan move the non-trivial relocation processing code out of head.S andreimplement it in C.Signed-off-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20240214122845.2033971-48-ardb+git@google.comSigned-off-by: Catalin Marinas List of files: /linux/arch/arm64/kernel/Makefile

d104a6fef3fec137d8d44961224ab76edbd6cbc7 - arm64: scs: Disable LTO for SCS patching code

Tue, 23 Jan 2024 14:30:55 +0100

arm64: scs: Disable LTO for SCS patching codeFull LTO takes the '-mbranch-protection=none' passed to the compilerwhen generating the dynamic shadow call stack patching code as a hint tostop emitting PAC instructions altogether. (Thin LTO appears unaffectedby this)Work around this by disabling LTO for the compilation unit, whichappears to convince the linker that it should still use PAC in the restof the kernel..Fixes: 3b619e22c460 ("arm64: implement dynamic shadow call stack for Clang")Signed-off-by: Ard Biesheuvel Reviewed-by: Kees Cook Reviewed-by: Sami Tolvanen Tested-by: Sami Tolvanen Link: https://lore.kernel.org/r/20240123133052.1417449-6-ardb+git@google.comSigned-off-by: Will Deacon List of files: /linux/arch/arm64/kernel/Makefile

2fa28abd1090562b4d9bc4aedd70abcca26561af - arm64: Revert "scs: Work around full LTO issue with dynamic SCS"

Tue, 23 Jan 2024 14:30:54 +0100

arm64: Revert "scs: Work around full LTO issue with dynamic SCS"This reverts commit 8c5a19cb17a71e ("arm64: scs: Work around full LTOissue with dynamic SCS"), which did not quite fix the issue as intended.Apparently, -fno-unwind-tables is ignored for the final full LTO linkwhen it is set on any of the objects, resulting in an early boot crashdue to the SCS patching code patching itself, and attempting to pop thereturn address from the shadow stack while the associated push was stilla PACIASP instruction when it executed.Reported-by: Sami Tolvanen Signed-off-by: Ard Biesheuvel Reviewed-by: Kees Cook Reviewed-by: Sami Tolvanen Tested-by: Sami Tolvanen Link: https://lore.kernel.org/r/20240123133052.1417449-5-ardb+git@google.comSigned-off-by: Will Deacon List of files: /linux/arch/arm64/kernel/Makefile

8c5a19cb17a71e52303150335b459c7d2d28a155 - arm64: scs: Work around full LTO issue with dynamic SCS

Wed, 10 Jan 2024 14:26:20 +0100

arm64: scs: Work around full LTO issue with dynamic SCSFull LTO takes the '-mbranch-protection=none' passed to the compilerwhen generating the dynamic shadow call stack patching code as a hint tostop emitting PAC instructions altogether. (Thin LTO appears unaffectedby this)Work around this by stripping unwind tables from the object in question,which should be sufficient to prevent the patching code from attemptingto patch itself.Fixes: 3b619e22c460 ("arm64: implement dynamic shadow call stack for Clang")Signed-off-by: Ard Biesheuvel Reviewed-by: Sami Tolvanen Reviewed-by: Kees Cook Link: https://lore.kernel.org/r/20240110132619.258809-2-ardb+git@google.comSigned-off-by: Will Deacon List of files: /linux/arch/arm64/kernel/Makefile

77b1a7f7a05c673c187894b4ae898a8c0cdc776c - Merge tag 'mm-nonmm-stable-2023-06-24-19-23' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

Wed, 28 Jun 2023 19:59:38 +0200

Merge tag 'mm-nonmm-stable-2023-06-24-19-23' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mmPull non-mm updates from Andrew Morton: - Arnd Bergmann has fixed a bunch of -Wmissing-prototypes in top-level directories - Douglas Anderson has added a new "buddy" mode to the hardlockup detector. It permits the detector to work on architectures which cannot provide the required interrupts, by having CPUs periodically perform checks on other CPUs - Zhen Lei has enhanced kexec's ability to support two crash regions - Petr Mladek has done a lot of cleanup on the hard lockup detector's Kconfig entries - And the usual bunch of singleton patches in various places* tag 'mm-nonmm-stable-2023-06-24-19-23' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm: (72 commits) kernel/time/posix-stubs.c: remove duplicated include ocfs2: remove redundant assignment to variable bit_off watchdog/hardlockup: fix typo in config HARDLOCKUP_DETECTOR_PREFER_BUDDY powerpc: move arch_trigger_cpumask_backtrace from nmi.h to irq.h devres: show which resource was invalid in __devm_ioremap_resource() watchdog/hardlockup: define HARDLOCKUP_DETECTOR_ARCH watchdog/sparc64: define HARDLOCKUP_DETECTOR_SPARC64 watchdog/hardlockup: make HAVE_NMI_WATCHDOG sparc64-specific watchdog/hardlockup: declare arch_touch_nmi_watchdog() only in linux/nmi.h watchdog/hardlockup: make the config checks more straightforward watchdog/hardlockup: sort hardlockup detector related config values a logical way watchdog/hardlockup: move SMP barriers from common code to buddy code watchdog/buddy: simplify the dependency for HARDLOCKUP_DETECTOR_PREFER_BUDDY watchdog/buddy: don't copy the cpumask in watchdog_next_cpu() watchdog/buddy: cleanup how watchdog_buddy_check_hardlockup() is called watchdog/hardlockup: remove softlockup comment in touch_nmi_watchdog() watchdog/hardlockup: in watchdog_hardlockup_check() use cpumask_copy() watchdog/hardlockup: don't use raw_cpu_ptr() in watchdog_hardlockup_kick() watchdog/hardlockup: HAVE_NMI_WATCHDOG must implement watchdog_hardlockup_probe() watchdog/hardlockup: keep kernel.nmi_watchdog sysctl as 0444 if probe fails ... List of files: /linux/arch/arm64/kernel/Makefile

94946f9eaac116f2943ec79ec3df1ec2fc92ae07 - arm64: add hw_nmi_get_sample_period for preparation of lockup detector

Fri, 19 May 2023 19:18:41 +0200

arm64: add hw_nmi_get_sample_period for preparation of lockup detectorSet safe maximum CPU frequency to 5 GHz in case a particular platformdoesn't implement cpufreq driver. Although, architecture doesn't put anyrestrictions on maximum frequency but 5 GHz seems to be safe maximum giventhe available Arm CPUs in the market which are clocked much less than 5GHz.On the other hand, we can't make it much higher as it would lead to alarge hard-lockup detection timeout on parts which are running slower (eg.1GHz on Developerbox) and doesn't possess a cpufreq driver.Link: https://lkml.kernel.org/r/20230519101840.v5.17.Ia9d02578e89c3f44d3cb12eec8b0176603c8ab2f@changeidCo-developed-by: Sumit Garg Signed-off-by: Sumit Garg Co-developed-by: Pingfan Liu Signed-off-by: Pingfan Liu Signed-off-by: Lecopzer Chen Signed-off-by: Douglas Anderson Cc: Andi Kleen Cc: Catalin Marinas Cc: Chen-Yu Tsai Cc: Christophe Leroy Cc: Colin Cross Cc: Daniel Thompson Cc: "David S. Miller" Cc: Guenter Roeck Cc: Ian Rogers Cc: Marc Zyngier Cc: Mark Rutland Cc: Masayoshi Mizuma Cc: Matthias Kaehlcke Cc: Michael Ellerman Cc: Nicholas Piggin Cc: Petr Mladek Cc: Randy Dunlap Cc: "Ravi V. Shankar" Cc: Ricardo Neri Cc: Stephane Eranian Cc: Stephen Boyd Cc: Tzung-Bi Shih Cc: Will Deacon Signed-off-by: Andrew Morton List of files: /linux/arch/arm64/kernel/Makefile

ea3752ba9685b47db4571ddaee39344cf2b0bf45 - arm64: module: mandate MODULE_PLTS

Tue, 30 May 2023 13:03:27 +0200

arm64: module: mandate MODULE_PLTSContemporary kernels and modules can be relatively large, especiallywhen common debug options are enabled. Using GCC 12.1.0, a v6.3-rc7defconfig kernel is ~38M, and with PROVE_LOCKING + KASAN_INLINE enabledthis expands to ~117M. Shanker reports [1] that the NVIDIA GPU driveralone can consume 110M of module space in some configurations.Both KASLR and ARM64_ERRATUM_843419 select MODULE_PLTS, so anyonewanting a kernel to have KASLR or run on Cortex-A53 will haveMODULE_PLTS selected. This is the case in defconfig and distributionkernels (e.g. Debian, Android, etc).Practically speaking, this means we're very likely to need MODULE_PLTSand while it's almost guaranteed that MODULE_PLTS will be selected, itis possible to disable support, and we have to maintain some awkwardspecial cases for such unusual configurations.This patch removes the MODULE_PLTS config option, with the support codealways enabled if MODULES is selected. This results in a slightsimplification, and will allow for further improvement in subsequentpatches.For any config which currently selects MODULE_PLTS, there will be nofunctional change as a result of this patch.[1] https://lore.kernel.org/linux-arm-kernel/159ceeab-09af-3174-5058-445bc8dcf85b@nvidia.com/Signed-off-by: Mark Rutland Reviewed-by: Ard Biesheuvel Cc: Shanker Donthineni Cc: Will Deacon Tested-by: Shanker Donthineni Link: https://lore.kernel.org/r/20230530110328.2213762-6-mark.rutland@arm.comSigned-off-by: Catalin Marinas List of files: /linux/arch/arm64/kernel/Makefile

7755cec63adeecea3cbbf4032047812c37cf7cc3 - arm64: perf: Move PMUv3 driver to drivers/perf

Fri, 17 Mar 2023 20:50:20 +0100

arm64: perf: Move PMUv3 driver to drivers/perfHaving the ARM PMUv3 driver sitting in arch/arm64/kernel is gettingin the way of being able to use perf on ARMv8 cores running a 32bitkernel, such as 32bit KVM guests.This patch moves it into drivers/perf/arm_pmuv3.c, with an includefile in include/linux/perf/arm_pmuv3.h. The only thing left inarch/arm64 is some mundane perf stuff.Signed-off-by: Marc Zyngier Signed-off-by: Zaid Al-Bassam Tested-by: Florian Fainelli Link: https://lore.kernel.org/r/20230317195027.3746949-2-zalbassam@google.comSigned-off-by: Will Deacon List of files: /linux/arch/arm64/kernel/Makefile

fc4c9f450493daef1c996c9d4b3c647ec3121509 - Merge tag 'efi-next-for-v6.2' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi

Tue, 13 Dec 2022 23:31:47 +0100

Merge tag 'efi-next-for-v6.2' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efiPull EFI updates from Ard Biesheuvel: "Another fairly sizable pull request, by EFI subsystem standards. Most of the work was done by me, some of it in collaboration with the distro and bootloader folks (GRUB, systemd-boot), where the main focus has been on removing pointless per-arch differences in the way EFI boots a Linux kernel. - Refactor the zboot code so that it incorporates all the EFI stub logic, rather than calling the decompressed kernel as a EFI app. - Add support for initrd= command line option to x86 mixed mode. - Allow initrd= to be used with arbitrary EFI accessible file systems instead of just the one the kernel itself was loaded from. - Move some x86-only handling and manipulation of the EFI memory map into arch/x86, as it is not used anywhere else. - More flexible handling of any random seeds provided by the boot environment (i.e., systemd-boot) so that it becomes available much earlier during the boot. - Allow improved arch-agnostic EFI support in loaders, by setting a uniform baseline of supported features, and adding a generic magic number to the DOS/PE header. This should allow loaders such as GRUB or systemd-boot to reduce the amount of arch-specific handling substantially. - (arm64) Run EFI runtime services from a dedicated stack, and use it to recover from synchronous exceptions that might occur in the firmware code. - (arm64) Ensure that we don't allocate memory outside of the 48-bit addressable physical range. - Make EFI pstore record size configurable - Add support for decoding CXL specific CPER records"* tag 'efi-next-for-v6.2' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi: (43 commits) arm64: efi: Recover from synchronous exceptions occurring in firmware arm64: efi: Execute runtime services from a dedicated stack arm64: efi: Limit allocations to 48-bit addressable physical region efi: Put Linux specific magic number in the DOS header efi: libstub: Always enable initrd command line loader and bump version efi: stub: use random seed from EFI variable efi: vars: prohibit reading random seed variables efi: random: combine bootloader provided RNG seed with RNG protocol output efi/cper, cxl: Decode CXL Error Log efi/cper, cxl: Decode CXL Protocol Error Section efi: libstub: fix efi_load_initrd_dev_path() kernel-doc comment efi: x86: Move EFI runtime map sysfs code to arch/x86 efi: runtime-maps: Clarify purpose and enable by default for kexec efi: pstore: Add module parameter for setting the record size efi: xen: Set EFI_PARAVIRT for Xen dom0 boot on all architectures efi: memmap: Move manipulation routines into x86 arch tree efi: memmap: Move EFI fake memmap support into x86 arch tree efi: libstub: Undeprecate the command line initrd loader efi: libstub: Add mixed mode support to command line initrd loader efi: libstub: Permit mixed mode return types other than efi_status_t ... List of files: /linux/arch/arm64/kernel/Makefile