Changes in Kconfig

0061b6e1 - mseal sysmap: enable arm64

Wed, 05 Mar 2025 02:17:08 +0000

mseal sysmap: enable arm64Provide support for CONFIG_MSEAL_SYSTEM_MAPPINGS on arm64, covering thevdso, vvar, and compat-mode vectors and sigpage mappings.Production release testing passes on Android and Chrome OS.Link: https://lkml.kernel.org/r/20250305021711.3867874-5-jeffxu@google.comSigned-off-by: Jeff Xu Reviewed-by: Lorenzo Stoakes Reviewed-by: Liam R. Howlett Reviewed-by: Kees Cook Cc: Adhemerval Zanella Cc: Alexander Mikhalitsyn Cc: Alexey Dobriyan Cc: Andrei Vagin Cc: Anna-Maria Behnsen Cc: Ard Biesheuvel Cc: Benjamin Berg Cc: Christoph Hellwig Cc: Dave Hansen Cc: David Rientjes Cc: David S. Miller Cc: Elliot Hughes Cc: Florian Faineli Cc: Greg Ungerer Cc: Guenter Roeck Cc: Heiko Carstens Cc: Helge Deller Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>Cc: Ingo Molnar Cc: Jann Horn Cc: Jason A. Donenfeld Cc: Johannes Berg Cc: Jorge Lucangeli Obes Cc: Linus Waleij Cc: Mark Rutland Cc: Matthew Wilcow (Oracle) Cc: Michael Ellerman Cc: Michal Hocko Cc: Miguel Ojeda Cc: Mike Rapoport Cc: Oleg Nesterov Cc: Pedro Falcato Cc: Peter Xu Cc: Randy Dunlap Cc: Stephen Röttger Cc: Thomas Weißschuh Cc: Vlastimil Babka Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/arm64/Kconfig

f9aad622 - mm: rename GENERIC_PTDUMP and PTDUMP_CORE

Wed, 26 Feb 2025 12:24:04 +0000

mm: rename GENERIC_PTDUMP and PTDUMP_COREPlatforms subscribe into generic ptdump implementation via GENERIC_PTDUMP.But generic ptdump gets enabled via PTDUMP_CORE. These configscombination is confusing as they sound very similar and does notdifferentiate between platform's feature subscription and featureenablement for ptdump. Rename the configs as ARCH_HAS_PTDUMP and PTDUMPmaking it more clear and improve readability.Link: https://lkml.kernel.org/r/20250226122404.1927473-6-anshuman.khandual@arm.comSigned-off-by: Anshuman Khandual Reviewed-by: Christophe Leroy (powerpc)Acked-by: Catalin Marinas [arm64]Cc: Will Deacon Cc: Jonathan Corbet Cc: Marc Zyngier Cc: Michael Ellerman Cc: Nicholas Piggin Cc: Paul Walmsley Cc: Palmer Dabbelt Cc: Heiko Carstens Cc: Vasily Gorbik Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Christophe Leroy Cc: Madhavan Srinivasan Cc: Mark Rutland Cc: Steven Price Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/arm64/Kconfig

eed4583b - arm64: Kconfig: Enable HOTPLUG_SMT

Tue, 11 Mar 2025 07:51:43 +0000

arm64: Kconfig: Enable HOTPLUG_SMTEnable HOTPLUG_SMT for SMT control.Reviewed-by: Jonathan Cameron Reviewed-by: Pierre Gondois Reviewed-by: Dietmar Eggemann Signed-off-by: Yicong Yang Reviewed-by: Sudeep Holla Link: https://lore.kernel.org/r/20250311075143.61078-5-yangyicong@huawei.comSigned-off-by: Catalin Marinas List of files: /linux-6.15/arch/arm64/Kconfig

51ecb29f - arm64/mm: Define PTDESC_ORDER

Tue, 11 Mar 2025 04:57:10 +0000

arm64/mm: Define PTDESC_ORDERAddress bytes shifted with a single 64 bit page table entry (any page tablelevel) has been always hard coded as 3 (aka 2^3 = 8). Although intuitive itis not very readable or easy to reason about. Besides it is going to changewith D128, where each 128 bit page table entry will shift address bytes by4 (aka 2^4 = 16) instead.Let's just formalise this address bytes shift value into a new macro calledPTDESC_ORDER establishing a logical abstraction, thus improving readabilityas well. While here re-organize EARLY_LEVEL macro along with its dependentsfor better clarity. This does not cause any functional change. Also replaceall (PAGE_SHIFT - PTDESC_ORDER) instances with PTDESC_TABLE_SHIFT.Cc: Will Deacon Cc: Mark Rutland Cc: Andrey Ryabinin Cc: Alexander Potapenko Cc: Andrey Konovalov Cc: Dmitry Vyukov Cc: Ard Biesheuvel Cc: Ryan Roberts Cc: linux-arm-kernel@lists.infradead.orgCc: linux-kernel@vger.kernel.orgCc: kasan-dev@googlegroups.comAcked-by: Ard Biesheuvel Reviewed-by: Ryan Roberts Signed-off-by: Anshuman Khandual Link: https://lore.kernel.org/r/20250311045710.550625-1-anshuman.khandual@arm.comSigned-off-by: Catalin Marinas List of files: /linux-6.15/arch/arm64/Kconfig

2d81e1bb - irqchip/gic-v3: Add Rockchip 3568002 erratum workaround

Sun, 16 Feb 2025 22:16:32 +0000

irqchip/gic-v3: Add Rockchip 3568002 erratum workaroundRockchip RK3566/RK3568 GIC600 integration has DDR addressinglimited to the first 32bit of physical address space. Rockchipassigned Erratum ID #3568002 for this issue. Add driver quirk forthis Rockchip GIC Erratum.Note, that the 0x0201743b GIC600 ID is not Rockchip-specific and iscommon for many ARM GICv3 implementations. Hence, there is an extraof_machine_is_compatible() check.Signed-off-by: Dmitry Osipenko Signed-off-by: Thomas Gleixner Acked-by: Marc Zyngier Link: https://lore.kernel.org/all/20250216221634.364158-2-dmitry.osipenko@collabora.com List of files: /linux-6.15/arch/arm64/Kconfig

0b3bc335 - arm64: vdso: Switch to generic storage implementation

Tue, 04 Feb 2025 12:05:40 +0000

arm64: vdso: Switch to generic storage implementationThe generic storage implementation provides the same features as thecustom one. However it can be shared between architectures, makingmaintenance easier.This switch also moves the random state data out of the time data page.The currently used hardcoded __VDSO_RND_DATA_OFFSET does not take intoaccount changes to the time data page layout.Co-developed-by: Nam Cao Signed-off-by: Nam Cao Signed-off-by: Thomas Weißschuh Signed-off-by: Thomas Gleixner Link: https://lore.kernel.org/all/20250204-vdso-store-rng-v3-8-13a4669dfc8c@linutronix.de List of files: /linux-6.15/arch/arm64/Kconfig

b3d09d06 - arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64

Tue, 18 Feb 2025 19:59:19 +0000

arm64: scripts/sorttable: Implement sorting mcount_loc at boot for arm64The mcount_loc section holds the addresses of the functions that getpatched by ftrace when enabling function callbacks. It can contain tens ofthousands of entries. These addresses must be sorted. If they are notsorted at compile time, they are sorted at boot. Sorting at boot does takesome time and does have a small impact on boot performance.x86 and arm32 have the addresses in the mcount_loc section of the ELFfile. But for arm64, the section just contains zeros. The .rela.dynElf_Rela section holds the addresses and they get patched at boot duringthe relocation phase.In order to sort these addresses, the Elf_Rela needs to be updated insteadof the location in the binary that holds the mcount_loc section. Have thesorttable code, allocate an array to hold the functions, load theaddresses from the Elf_Rela entries, sort them, then put them back inorder into the Elf_rela entries so that they will be sorted at boot upwithout having to sort them during boot up.Cc: bpf Cc: Masami Hiramatsu Cc: Mark Rutland Cc: Mathieu Desnoyers Cc: Andrew Morton Cc: Peter Zijlstra Cc: Linus Torvalds Cc: Masahiro Yamada Cc: Nathan Chancellor Cc: Nicolas Schier Cc: Zheng Yejian Cc: Martin Kelly Cc: Christophe Leroy Cc: Josh Poimboeuf Cc: Heiko Carstens Cc: Will Deacon Cc: Vasily Gorbik Cc: Alexander Gordeev Link: https://lore.kernel.org/20250218200022.373319428@goodmis.orgAcked-by: Catalin Marinas Signed-off-by: Steven Rostedt (Google) List of files: /linux-6.15/arch/arm64/Kconfig

f458b216 - arm64: Kconfig: Remove selecting replaced HAVE_FUNCTION_GRAPH_RETVAL

Fri, 17 Jan 2025 12:55:22 +0000

arm64: Kconfig: Remove selecting replaced HAVE_FUNCTION_GRAPH_RETVALCommit a3ed4157b7d8 ("fgraph: Replace fgraph_ret_regs with ftrace_regs")replaces the config HAVE_FUNCTION_GRAPH_RETVAL with the configHAVE_FUNCTION_GRAPH_FREGS, and it replaces all the select commands in thevarious architecture Kconfig files. In the arm64 architecture, the commitadds the 'select HAVE_FUNCTION_GRAPH_FREGS', but misses to remove the'select HAVE_FUNCTION_GRAPH_RETVAL', i.e., the select on the replacedconfig.Remove selecting the replaced config. No functional change, just cleanup.Fixes: a3ed4157b7d8 ("fgraph: Replace fgraph_ret_regs with ftrace_regs")Signed-off-by: Lukas Bulwahn Link: https://lore.kernel.org/r/20250117125522.99071-1-lukas.bulwahn@redhat.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/Kconfig

a762e926 - ftrace: Add CONFIG_HAVE_FTRACE_GRAPH_FUNC

Thu, 26 Dec 2024 05:13:34 +0000

ftrace: Add CONFIG_HAVE_FTRACE_GRAPH_FUNCAdd CONFIG_HAVE_FTRACE_GRAPH_FUNC kconfig in addition to ftrace_graph_funcmacro check. This is for the other feature (e.g. FPROBE) which requires toaccess ftrace_regs from fgraph_ops::entryfunc() can avoid compiling ifthe fgraph can not pass the valid ftrace_regs.Signed-off-by: Masami Hiramatsu (Google) Cc: Catalin Marinas Cc: Alexei Starovoitov Cc: Florent Revest Cc: Martin KaFai Lau Cc: bpf Cc: Alexei Starovoitov Cc: Jiri Olsa Cc: Alan Maguire Cc: Mark Rutland Cc: Will Deacon Cc: Huacai Chen Cc: WANG Xuerui Cc: Michael Ellerman Cc: Nicholas Piggin Cc: Christophe Leroy Cc: Naveen N Rao Cc: Madhavan Srinivasan Cc: Paul Walmsley Cc: Palmer Dabbelt Cc: Albert Ou Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Borislav Petkov Cc: Dave Hansen Cc: x86@kernel.orgCc: "H. Peter Anvin" Cc: Mathieu Desnoyers Link: https://lore.kernel.org/173519001472.391279.1174901685282588467.stgit@devnote2Signed-off-by: Steven Rostedt (Google) List of files: /linux-6.15/arch/arm64/Kconfig

a3ed4157 - fgraph: Replace fgraph_ret_regs with ftrace_regs

Thu, 26 Dec 2024 05:11:55 +0000

fgraph: Replace fgraph_ret_regs with ftrace_regsUse ftrace_regs instead of fgraph_ret_regs for tracing return valueon function_graph tracer because of simplifying the callback interface.The CONFIG_HAVE_FUNCTION_GRAPH_RETVAL is also replaced byCONFIG_HAVE_FUNCTION_GRAPH_FREGS.Signed-off-by: Masami Hiramatsu (Google) Acked-by: Heiko Carstens Acked-by: Will Deacon Cc: Catalin Marinas Cc: Alexei Starovoitov Cc: Florent Revest Cc: Martin KaFai Lau Cc: bpf Cc: Alexei Starovoitov Cc: Jiri Olsa Cc: Alan Maguire Cc: Mark Rutland Cc: Huacai Chen Cc: WANG Xuerui Cc: Paul Walmsley Cc: Palmer Dabbelt Cc: Albert Ou Cc: Vasily Gorbik Cc: Alexander Gordeev Cc: Heiko Carstens Cc: Christian Borntraeger Cc: Sven Schnelle Cc: Thomas Gleixner Cc: Ingo Molnar Cc: Borislav Petkov Cc: Dave Hansen Cc: x86@kernel.orgCc: "H. Peter Anvin" Cc: Mathieu Desnoyers Link: https://lore.kernel.org/173518991508.391279.16635322774382197642.stgit@devnote2Signed-off-by: Steven Rostedt (Google) List of files: /linux-6.15/arch/arm64/Kconfig

92b6919d - arm64: Kconfig: force ARM64_PAN=y when enabling TTBR0 sw PAN

Thu, 12 Dec 2024 08:18:47 +0000

arm64: Kconfig: force ARM64_PAN=y when enabling TTBR0 sw PANThere are a couple of instances of Kconfig constraints where PAN must beenabled too if TTBR0 sw PAN is enabled, primarily to avoid dealing withthe modified TTBR0_EL1 sysreg format that is used when 52-bit physicaladdressing and/or CnP are enabled (support for either implies supportfor hardware PAN as well, which will supersede PAN emulation if both areavailable)Let's simplify this, and always enable ARM64_PAN when enabling TTBR0 swPAN. This decouples the PAN configuration from the VA size selection,permitting us to simplify the latter in subsequent patches. (Note thatPAN and TTBR0 sw PAN can still be disabled after this patch, but notindependently)To avoid a convoluted circular Kconfig dependency involving KCSAN, makeARM64_MTE select ARM64_PAN too, instead of depending on it.Signed-off-by: Ard Biesheuvel Acked-by: Marc Zyngier Link: https://lore.kernel.org/r/20241212081841.2168124-13-ardb+git@google.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/Kconfig

9456a159 - arm64/Kconfig: Drop EXECMEM dependency from ARCH_WANTS_EXECMEM_LATE

Tue, 10 Dec 2024 04:32:57 +0000

arm64/Kconfig: Drop EXECMEM dependency from ARCH_WANTS_EXECMEM_LATEARCH_WANTS_EXECMEM_LATE indicates subscribing platform's preference forEXECMEM late initialisation without creating a new dependency. Hence thisjust drops EXECMEM dependency while selecting ARCH_WANTS_EXECMEM_LATE.Cc: Catalin Marinas Cc: Will Deacon Cc: Andrew Morton Cc: linux-arm-kernel@lists.infradead.orgCc: linux-mm@kvack.orgCc: linux-kernel@vger.kernel.orgSigned-off-by: Anshuman Khandual Link: https://lore.kernel.org/r/20241210043257.715822-1-anshuman.khandual@arm.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/Kconfig

bad6722e - kexec: Consolidate machine_kexec_mask_interrupts() implementation

Wed, 04 Dec 2024 14:20:02 +0000

kexec: Consolidate machine_kexec_mask_interrupts() implementationConsolidate the machine_kexec_mask_interrupts implementation into a commonfunction located in a new file: kernel/irq/kexec.c. This removes duplicateimplementations from architecture-specific files in arch/arm, arch/arm64,arch/powerpc, and arch/riscv, reducing code duplication and improvingmaintainability.The new implementation retains architecture-specific behavior forCONFIG_GENERIC_IRQ_KEXEC_CLEAR_VM_FORWARD, which was previously implementedfor ARM64. When enabled (currently for ARM64), it clears the active stateof interrupts forwarded to virtual machines (VMs) before handling otherinterrupt masking operations.Signed-off-by: Eliav Farber Signed-off-by: Thomas Gleixner Link: https://lore.kernel.org/all/20241204142003.32859-2-farbere@amazon.com List of files: /linux-6.15/arch/arm64/Kconfig

2051da85 - arm64/crc-t10dif: expose CRC-T10DIF function through lib

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

arm64/crc-t10dif: expose CRC-T10DIF function through libMove the arm64 CRC-T10DIF assembly code into the lib directory and wireit up 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/arm64/crypto/crct10dif-ce-glue.c toarch/arm64/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-7-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux-6.15/arch/arm64/Kconfig

d36cebe0 - lib/crc32: improve support for arch-specific overrides

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

lib/crc32: improve support for arch-specific overridesCurrently the CRC32 library functions are defined as weak symbols, andthe arm64 and riscv architectures override them.This method of arch-specific overrides has the limitation that it onlyworks when both the base and arch code is built-in. Also, it makes thearch-specific code be silently not used if it is accidentally built withlib-y instead of obj-y; unfortunately the RISC-V code does this.This commit reorganizes the code to have explicit *_arch() functionsthat are called when they are enabled, similar to how some of the cryptolibrary code works (e.g. chacha_crypt() calls chacha_crypt_arch()).Make the existing kconfig choice for the CRC32 implementation alsocontrol whether the arch-optimized implementation (if one is available)is enabled or not. Make it enabled by default if CRC32 is also enabled.The result is that arch-optimized CRC32 library functions will beincluded automatically when appropriate, but it is now possible todisable them. They can also now be built as a loadable module if theCRC32 library functions happen to be used only by loadable modules, inwhich case the arch and base CRC32 modules will be automatically loadedvia direct symbol dependency when appropriate.Reviewed-by: Ard Biesheuvel Link: https://lore.kernel.org/r/20241202010844.144356-3-ebiggers@kernel.orgSigned-off-by: Eric Biggers List of files: /linux-6.15/arch/arm64/Kconfig

f82e62d4 - irqchip/gicv3-its: Add workaround for hip09 ITS erratum 162100801

Sat, 16 Nov 2024 08:01:26 +0000

irqchip/gicv3-its: Add workaround for hip09 ITS erratum 162100801When enabling GICv4.1 in hip09, VMAPP fails to clear some caches duringthe unmap operation, which can causes vSGIs to be lost.To fix the issue, invalidate the related vPE cache through GICR_INVALLRafter VMOVP.Suggested-by: Marc Zyngier Co-developed-by: Nianyao Tang Signed-off-by: Nianyao Tang Signed-off-by: Zhou Wang Signed-off-by: Thomas Gleixner Reviewed-by: Marc Zyngier List of files: /linux-6.15/arch/arm64/Kconfig

a63d7408 - arm64: disable ARCH_CORRECT_STACKTRACE_ON_KRETPROBE tests

Mon, 18 Nov 2024 12:02:04 +0000

arm64: disable ARCH_CORRECT_STACKTRACE_ON_KRETPROBE testsThe kprobes_test suite's test_stacktrace_on_nested_kretprobe() testcurrently fails on arm64, e.g.| KTAP version 1| 1..1| KTAP version 1| # Subtest: kprobes_test| # module: test_kprobes| 1..7| ok 1 test_kprobe| ok 2 test_kprobes| ok 3 test_kprobe_missed| ok 4 test_kretprobe| ok 5 test_kretprobes| ok 6 test_stacktrace_on_kretprobe| # test_stacktrace_on_nested_kretprobe: EXPECTATION FAILED at lib/test_kprobes.c:327| Expected stack_buf[i + 1] == target_return_address[1], but| stack_buf[i + 1] == -96519936577004 (0xffffa83733777214)| target_return_address[1] == -96519936577136 (0xffffa83733777190)| # test_stacktrace_on_nested_kretprobe: EXPECTATION FAILED at lib/test_kprobes.c:338| Expected stack_buf[1] == target_return_address[1], but| stack_buf[1] == -96519936577004 (0xffffa83733777214)| target_return_address[1] == -96519936577136 (0xffffa83733777190)| not ok 7 test_stacktrace_on_nested_kretprobe| # kprobes_test: pass:6 fail:1 skip:0 total:7| # Totals: pass:6 fail:1 skip:0 total:7| not ok 1 kprobes_testThe test assumes that when a stacktrace straddles an exception boundary,no necessary entries will be omitted and no extraneous entries will bereported, and when unwinding from a kretprobed callee, the next entry inthe trace will be its immediate caller (whether kretprobed or not).Recently the arm64 stacktrace code was changed to always report the LRat an exception boundary, where we don't know whether the LR is live.In the case of the kretprobe trampoline the LR is not live at the timethe stacktrace is performed, and so the entry in the trace for the LR isextraneous. This can be seen if a call to show_stack() is added tostacktrace_internal_return_handler():| Call trace:| show_stack+0x18/0x30 (C)| stacktrace_internal_return_handler+0x130/0x43c| __kretprobe_trampoline_handler+0xa0/0x130| kretprobe_breakpoint_handler+0x50/0x70| call_break_hook+0x74/0x8c| brk_handler+0x1c/0x60| do_debug_exception+0x68/0x114| el1_dbg+0x70/0x94| el1h_64_sync_handler+0xc4/0xe4| el1h_64_sync+0x6c/0x70| kprobe_stacktrace_target+0x34/0x48 (P)| kprobe_stacktrace_target+0x34/0x48 (LK) <-------- extra entry here| kprobe_stacktrace_driver+0x24/0x40 (K)| test_stacktrace_on_nested_kretprobe+0x84/0x160| kunit_try_run_case+0x6c/0x160| kunit_generic_run_threadfn_adapter+0x28/0x4c| kthread+0x110/0x114| ret_from_fork+0x10/0x20This breaks test_stacktrace_on_nested_kretprobe() because while thecaller (kprobe_stacktrace_driver()) appears in the trace, it doesn'toccur *immediately* after the first instance of callee(kprobe_stacktrace_target()).While this behaviour is unfortunate for the kretprobes tests, thebehaviour is desirable elsewhere (e.g. anywhere a human will read thetrace), and is otherwise not harmful.For the moment, deselect ARCH_CORRECT_STACKTRACE_ON_KRETPROBE on arm64to disable the tests which depend on this behaviour. WithARCH_CORRECT_STACKTRACE_ON_KRETPROBE deselected, the remaining testswork as expected, e.g.| KTAP version 1| 1..1| KTAP version 1| # Subtest: kprobes_test| # module: test_kprobes| 1..5| ok 1 test_kprobe| ok 2 test_kprobes| ok 3 test_kprobe_missed| ok 4 test_kretprobe| ok 5 test_kretprobes| # kprobes_test: pass:5 fail:0 skip:0 total:5| # Totals: pass:5 fail:0 skip:0 total:5| ok 1 kprobes_testIn future we have several options to improve matters, e.g.* Add metadata and update arm64's unwinder to skip the LR in this case. This is likely to happen as part of work for RELIABLE_STACKTRACE for other reasons, and might solve this case by coincidence.* Modify the kretprobes tests to only require that the caller appears in the trace after the callee, rather than requiring that it is *immediately* after the callee. We might want separate strict/not-strict options for this.* Use reliable stacktrace for these tests, so that architectures which cannot unwind across exception boundaries can explicitly handle this by returning an error.Fixes: c2c6b27b5aa1 ("arm64: stacktrace: unwind exception boundaries")Signed-off-by: Mark Rutland Reported-by: Kristina Martsenko Cc: Ard Biesheuvel Cc: Josh Poimboeuf Cc: Kalesh Singh Cc: Madhavan T. Venkataraman Cc: Marc Zyngier Cc: Mark Brown Cc: Masami Hiramatsu Cc: Miroslav Benes Cc: Puranjay Mohan Cc: Steven Rostedt Cc: Will Deacon Reviewed-by: Mark Brown Link: https://lore.kernel.org/r/20241118120204.3961548-1-mark.rutland@arm.comSigned-off-by: Catalin Marinas List of files: /linux-6.15/arch/arm64/Kconfig

31daa343 - crash, powerpc: default to CRASH_DUMP=n on PPC_BOOK3S_32

Tue, 17 Sep 2024 16:37:20 +0000

crash, powerpc: default to CRASH_DUMP=n on PPC_BOOK3S_32Fixes boot failures on 6.9 on PPC_BOOK3S_32 machines using Open Firmware. On these machines, the kernel refuses to boot from non-zeroPHYSICAL_START, which occurs when CRASH_DUMP is on.Since most PPC_BOOK3S_32 machines boot via Open Firmware, it shoulddefault to off for them. Users booting via some other mechanism can stillturn it on explicitly.Does not change the default on any other architectures for thetime being.Link: https://lkml.kernel.org/r/20240917163720.1644584-1-dave@vasilevsky.caFixes: 75bc255a7444 ("crash: clean up kdump related config items")Signed-off-by: Dave Vasilevsky Reported-by: Reimar Döffinger Closes: https://lists.debian.org/debian-powerpc/2024/07/msg00001.htmlAcked-by: Michael Ellerman [powerpc]Acked-by: Baoquan He Cc: "Eric W. Biederman" Cc: John Paul Adrian Glaubitz Cc: Reimar Döffinger Cc: Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/arm64/Kconfig

81235ae0 - arm64: Kconfig: Make SME depend on BROKEN for now

Wed, 06 Nov 2024 16:42:20 +0000

arm64: Kconfig: Make SME depend on BROKEN for nowAlthough support for SME was merged in v5.19, we've since uncovered anumber of issues with the implementation, including issues which mightcorrupt the FPSIMD/SVE/SME state of arbitrary tasks. While there arepatches to address some of these issues, ongoing review has highlightedadditional functional problems, and more time is necessary to analyseand fix these.For now, mark SME as BROKEN in the hope that we can fix things properlyin the near future. As SME is an OPTIONAL part of ARMv9.2+, and there isvery little extant hardware, this should not adversely affect the vastmajority of users.Signed-off-by: Mark Rutland Cc: Ard Biesheuvel Cc: Catalin Marinas Cc: Marc Zyngier Cc: Mark Brown Cc: Will Deacon Cc: stable@vger.kernel.org # 5.19Acked-by: Catalin Marinas Link: https://lore.kernel.org/r/20241106164220.2789279-1-mark.rutland@arm.comSigned-off-by: Will Deacon List of files: /linux-6.15/arch/arm64/Kconfig

62df5870 - arm64: Enable ARCH_HAS_NONLEAF_PMD_YOUNG

Sat, 02 Nov 2024 10:42:34 +0000

arm64: Enable ARCH_HAS_NONLEAF_PMD_YOUNGWith the support of FEAT_HAFT, the NONLEAF_PMD_YOUNG can be enabledon arm64 since the hardware is capable of updating the AF flag forPMD table descriptor. Since the AF bit of the table descriptorshares the same bit position in block descriptors, we only needto implement arch_has_hw_nonleaf_pmd_young() and select relatedconfigs. The related pmd_young test/update operations keeps thesame with and already implemented for transparent page support.Currently ARCH_HAS_NONLEAF_PMD_YOUNG is used to improve theefficiency of lru-gen aging.Signed-off-by: Yicong Yang Reviewed-by: Catalin Marinas Link: https://lore.kernel.org/r/20241102104235.62560-5-yangyicong@huawei.comSigned-off-by: Catalin Marinas List of files: /linux-6.15/arch/arm64/Kconfig