Changes in Kconfig

5394f1e9 - arch: define CONFIG_PAGE_SIZE_*KB on all architectures

Mon, 26 Feb 2024 16:14:13 +0000

arch: define CONFIG_PAGE_SIZE_*KB on all architecturesMost architectures only support a single hardcoded page size. In orderto ensure that each one of these sets the corresponding Kconfig symbols,change over the PAGE_SHIFT definition to the common one and allowonly the hardware page size to be selected.Acked-by: Guo Ren Acked-by: Heiko Carstens Acked-by: Stafford Horne Acked-by: Johannes Berg Acked-by: Geert Uytterhoeven Reviewed-by: Thomas Gleixner Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/nios2/Kconfig

8690bbcf - Introduce cpu_dcache_is_aliasing() across all architectures

Thu, 15 Feb 2024 14:46:32 +0000

Introduce cpu_dcache_is_aliasing() across all architecturesIntroduce a generic way to query whether the data cache is virtuallyaliased on all architectures. Its purpose is to ensure that subsystemswhich are incompatible with virtually aliased data caches (e.g. FS_DAX)can reliably query this.For data cache aliasing, there are three scenarios dependending on thearchitecture. Here is a breakdown based on my understanding:A) The data cache is always aliasing:* arc* csky* m68k (note: shared memory mappings are incoherent ? SHMLBA is missing there.)* sh* pariscB) The data cache aliasing is statically known or depends on querying CPU state at runtime:* arm (cache_is_vivt() || cache_is_vipt_aliasing())* mips (cpu_has_dc_aliases)* nios2 (NIOS2_DCACHE_SIZE > PAGE_SIZE)* sparc32 (vac_cache_size > PAGE_SIZE)* sparc64 (L1DCACHE_SIZE > PAGE_SIZE)* xtensa (DCACHE_WAY_SIZE > PAGE_SIZE)C) The data cache is never aliasing:* alpha* arm64 (aarch64)* hexagon* loongarch (but with incoherent write buffers, which are disabled since commit d23b7795 ("LoongArch: Change SHMLBA from SZ_64K to PAGE_SIZE"))* microblaze* openrisc* powerpc* riscv* s390* um* x86Require architectures in A) and B) to select ARCH_HAS_CPU_CACHE_ALIASING andimplement "cpu_dcache_is_aliasing()".Architectures in C) don't select ARCH_HAS_CPU_CACHE_ALIASING, and thuscpu_dcache_is_aliasing() simply evaluates to "false".Note that this leaves "cpu_icache_is_aliasing()" to be implemented as futurework. This would be useful to gate features like XIP on architectureswhich have aliasing CPU dcache-icache but not CPU dcache-dcache.Use "cpu_dcache" and "cpu_cache" rather than just "dcache" and "cache"to clarify that we really mean "CPU data cache" and "CPU cache" toeliminate any possible confusion with VFS "dentry cache" and "pagecache".Link: https://lore.kernel.org/lkml/20030910210416.GA24258@mail.jlokier.co.uk/Link: https://lkml.kernel.org/r/20240215144633.96437-9-mathieu.desnoyers@efficios.comFixes: d92576f1167c ("dax: does not work correctly with virtual aliasing caches")Signed-off-by: Mathieu Desnoyers Cc: Dan Williams Cc: Vishal Verma Cc: Dave Jiang Cc: Matthew Wilcox Cc: Arnd Bergmann Cc: Russell King Cc: Alasdair Kergon Cc: Christoph Hellwig Cc: Dave Chinner Cc: Heiko Carstens Cc: kernel test robot Cc: Michael Sclafani Cc: Mike Snitzer Cc: Mikulas Patocka Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

5e0a760b - mm, treewide: rename MAX_ORDER to MAX_PAGE_ORDER

Thu, 28 Dec 2023 14:47:04 +0000

mm, treewide: rename MAX_ORDER to MAX_PAGE_ORDERcommit 23baf831a32c ("mm, treewide: redefine MAX_ORDER sanely") haschanged the definition of MAX_ORDER to be inclusive. This has causedissues with code that was not yet upstream and depended on the previousdefinition.To draw attention to the altered meaning of the define, rename MAX_ORDERto MAX_PAGE_ORDER.Link: https://lkml.kernel.org/r/20231228144704.14033-2-kirill.shutemov@linux.intel.comSigned-off-by: Kirill A. Shutemov Cc: Linus Torvalds Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

a050ba1e - mm/fault: convert remaining simple cases to lock_mm_and_find_vma()

Sat, 24 Jun 2023 17:55:38 +0000

mm/fault: convert remaining simple cases to lock_mm_and_find_vma()This does the simple pattern conversion of alpha, arc, csky, hexagon,loongarch, nios2, sh, sparc32, and xtensa to the lock_mm_and_find_vma()helper. They all have the regular fault handling pattern without oddspecial cases.The remaining architectures all have something that keeps us from astraightforward conversion: ia64 and parisc have stacks that can growboth up as well as down (and ia64 has special address region checks).And m68k, microblaze, openrisc, sparc64, and um end up having extrarules about only expanding the stack down a limited amount below theuser space stack pointer. That is something that x86 used to do too(long long ago), and it probably could just be skipped, but it stillmakes the conversion less than trivial.Note that this conversion was done manually and with the exception ofalpha without any build testing, because I have a fairly limited cross-building environment. The cases are all simple, and I went through thechanges several times, but...Signed-off-by: Linus Torvalds List of files: /linux-6.15/arch/nios2/Kconfig

482f7b76 - nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER

Fri, 24 Mar 2023 05:22:27 +0000

nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDERnios2 defines range for ARCH_FORCE_MAX_ORDER allowing MAX_ORDER up to 19,which implies maximal contiguous allocation size of 2^19 pages or 2GiB.Drop bogus definition of ranges for ARCH_FORCE_MAX_ORDER and leave it asimple integer with sensible default.Users that *really* need to change the value of ARCH_FORCE_MAX_ORDER willbe able to do so but they won't be mislead by the bogus ranges.Link: https://lkml.kernel.org/r/20230324052233.2654090-9-rppt@kernel.orgSigned-off-by: Mike Rapoport (IBM) Acked-by: Kirill A. Shutemov Reviewed-by: Zi Yan Cc: Arnd Bergmann Cc: Catalin Marinas Cc: Christophe Leroy Cc: David Miller Cc: Dinh Nguyen Cc: Geert Uytterhoeven Cc: Guo Ren Cc: John Paul Adrian Glaubitz Cc: Max Filippov Cc: Michael Ellerman Cc: Rich Felker Cc: "Russell King (Oracle)" Cc: Will Deacon Cc: Yoshinori Sato Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

5646e83d - nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text

Fri, 24 Mar 2023 05:22:26 +0000

nios2: reword ARCH_FORCE_MAX_ORDER prompt and help textThe prompt and help text of ARCH_FORCE_MAX_ORDER are not even close todescribe this configuration option.Update both to actually describe what this option does.Link: https://lkml.kernel.org/r/20230324052233.2654090-8-rppt@kernel.orgSigned-off-by: Mike Rapoport (IBM) Acked-by: Kirill A. Shutemov Reviewed-by: Zi Yan Cc: Arnd Bergmann Cc: Catalin Marinas Cc: Christophe Leroy Cc: David Miller Cc: Dinh Nguyen Cc: Geert Uytterhoeven Cc: Guo Ren Cc: John Paul Adrian Glaubitz Cc: Max Filippov Cc: Michael Ellerman Cc: Rich Felker Cc: "Russell King (Oracle)" Cc: Will Deacon Cc: Yoshinori Sato Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

23baf831 - mm, treewide: redefine MAX_ORDER sanely

Wed, 15 Mar 2023 11:31:33 +0000

mm, treewide: redefine MAX_ORDER sanelyMAX_ORDER currently defined as number of orders page allocator supports:user can ask buddy allocator for page order between 0 and MAX_ORDER-1.This definition is counter-intuitive and lead to number of bugs all overthe kernel.Change the definition of MAX_ORDER to be inclusive: the range of ordersuser can ask from buddy allocator is 0..MAX_ORDER now.[kirill@shutemov.name: fix min() warning] Link: https://lkml.kernel.org/r/20230315153800.32wib3n5rickolvh@box[akpm@linux-foundation.org: fix another min_t warning][kirill@shutemov.name: fixups per Zi Yan] Link: https://lkml.kernel.org/r/20230316232144.b7ic4cif4kjiabws@box.shutemov.name[akpm@linux-foundation.org: fix underlining in docs] Link: https://lore.kernel.org/oe-kbuild-all/202303191025.VRCTk6mP-lkp@intel.com/Link: https://lkml.kernel.org/r/20230315113133.11326-11-kirill.shutemov@linux.intel.comSigned-off-by: Kirill A. Shutemov Reviewed-by: Michael Ellerman [powerpc]Cc: "Kirill A. Shutemov" Cc: Zi Yan Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

0192445c - arch: mm: rename FORCE_MAX_ZONEORDER to ARCH_FORCE_MAX_ORDER

Mon, 15 Aug 2022 14:39:59 +0000

arch: mm: rename FORCE_MAX_ZONEORDER to ARCH_FORCE_MAX_ORDERThis Kconfig option is used by individual arch to set its desiredMAX_ORDER. Rename it to reflect its actual use.Link: https://lkml.kernel.org/r/20220815143959.1511278-1-zi.yan@sent.comAcked-by: Mike Rapoport Signed-off-by: Zi Yan Acked-by: Guo Ren [csky]Acked-by: Arnd Bergmann Acked-by: Catalin Marinas [arm64]Acked-by: Huacai Chen [LoongArch]Acked-by: Michael Ellerman [powerpc]Cc: Vineet Gupta Cc: Taichi Sugaya Cc: Neil Armstrong Cc: Qin Jian Cc: Guo Ren Cc: Geert Uytterhoeven Cc: Thomas Bogendoerfer Cc: Dinh Nguyen Cc: Christophe Leroy Cc: Yoshinori Sato Cc: "David S. Miller" Cc: Chris Zankel Cc: Ley Foon Tan Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

3d923c5f - mm/mmap: drop ARCH_HAS_VM_GET_PAGE_PROT

Mon, 11 Jul 2022 07:06:00 +0000

mm/mmap: drop ARCH_HAS_VM_GET_PAGE_PROTNow all the platforms enable ARCH_HAS_GET_PAGE_PROT. They define andexport own vm_get_page_prot() whether custom or standardDECLARE_VM_GET_PAGE_PROT. Hence there is no need for default genericfallback for vm_get_page_prot(). Just drop this fallback and alsoARCH_HAS_GET_PAGE_PROT mechanism.Link: https://lkml.kernel.org/r/20220711070600.2378316-27-anshuman.khandual@arm.comSigned-off-by: Anshuman Khandual Reviewed-by: Geert Uytterhoeven Reviewed-by: Christoph Hellwig Reviewed-by: Christophe Leroy Acked-by: Geert Uytterhoeven Cc: Arnd Bergmann Cc: Brian Cain Cc: Catalin Marinas Cc: Christoph Hellwig Cc: Chris Zankel Cc: "David S. Miller" Cc: Dinh Nguyen Cc: Guo Ren Cc: Heiko Carstens Cc: Huacai Chen Cc: Ingo Molnar Cc: "James E.J. Bottomley" Cc: Jeff Dike Cc: Jonas Bonn Cc: Michael Ellerman Cc: Michal Simek Cc: Nicholas Piggin Cc: Palmer Dabbelt Cc: Paul Mackerras Cc: Paul Walmsley Cc: Richard Henderson Cc: Rich Felker Cc: Russell King Cc: Sam Ravnborg Cc: Stafford Horne Cc: Thomas Bogendoerfer Cc: Thomas Gleixner Cc: Vasily Gorbik Cc: Vineet Gupta Cc: WANG Xuerui Cc: Will Deacon Cc: Yoshinori Sato Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

53e2fdee - nios2/mm: enable ARCH_HAS_VM_GET_PAGE_PROT

Mon, 11 Jul 2022 07:05:49 +0000

nios2/mm: enable ARCH_HAS_VM_GET_PAGE_PROTThis enables ARCH_HAS_VM_GET_PAGE_PROT on the platform and exportsstandard vm_get_page_prot() implementation via DECLARE_VM_GET_PAGE_PROT,which looks up a private and static protection_map[] array. Subsequentlyall __SXXX and __PXXX macros can be dropped which are no longer needed.Link: https://lkml.kernel.org/r/20220711070600.2378316-16-anshuman.khandual@arm.comSigned-off-by: Anshuman Khandual Acked-by: Dinh Nguyen Cc: Arnd Bergmann Cc: Brian Cain Cc: Catalin Marinas Cc: Christophe Leroy Cc: Christoph Hellwig Cc: Christoph Hellwig Cc: Chris Zankel Cc: "David S. Miller" Cc: Geert Uytterhoeven Cc: Guo Ren Cc: Heiko Carstens Cc: Huacai Chen Cc: Ingo Molnar Cc: "James E.J. Bottomley" Cc: Jeff Dike Cc: Jonas Bonn Cc: Michael Ellerman Cc: Michal Simek Cc: Nicholas Piggin Cc: Palmer Dabbelt Cc: Paul Mackerras Cc: Paul Walmsley Cc: Richard Henderson Cc: Rich Felker Cc: Russell King Cc: Sam Ravnborg Cc: Stafford Horne Cc: Thomas Bogendoerfer Cc: Thomas Gleixner Cc: Vasily Gorbik Cc: Vineet Gupta Cc: WANG Xuerui Cc: Will Deacon Cc: Yoshinori Sato Signed-off-by: Andrew Morton List of files: /linux-6.15/arch/nios2/Kconfig

967747bb - uaccess: remove CONFIG_SET_FS

Fri, 11 Feb 2022 20:42:45 +0000

uaccess: remove CONFIG_SET_FSThere are no remaining callers of set_fs(), so CONFIG_SET_FScan be removed globally, along with the thread_info field andany references to it.This turns access_ok() into a cheaper check against TASK_SIZE_MAX.As CONFIG_SET_FS is now gone, drop all remaining references toset_fs()/get_fs(), mm_segment_t, user_addr_max() and uaccess_kernel().Acked-by: Sam Ravnborg # for sparc32 changesAcked-by: "Eric W. Biederman" Tested-by: Sergey Matyukevich # for arc changesAcked-by: Stafford Horne # [openrisc, asm-generic]Acked-by: Dinh Nguyen Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/nios2/Kconfig

4aae683f - tracing: Refactor TRACE_IRQFLAGS_SUPPORT in Kconfig

Sat, 31 Jul 2021 05:22:32 +0000

tracing: Refactor TRACE_IRQFLAGS_SUPPORT in KconfigMake architectures select TRACE_IRQFLAGS_SUPPORT instead ofhaving many defines.Link: https://lkml.kernel.org/r/20210731052233.4703-2-masahiroy@kernel.orgAcked-by: Heiko Carstens Acked-by: Vineet Gupta #arch/arcAcked-by: Michael Ellerman (powerpc)Acked-by: Catalin Marinas Acked-by: Max Filippov Signed-off-by: Masahiro Yamada Signed-off-by: Steven Rostedt (VMware) List of files: /linux-6.15/arch/nios2/Kconfig

e6226997 - asm-generic: reverse GENERIC_{STRNCPY_FROM,STRNLEN}_USER symbols

Mon, 17 May 2021 07:22:34 +0000

asm-generic: reverse GENERIC_{STRNCPY_FROM,STRNLEN}_USER symbolsMost architectures do not need a custom implementation, and in mostcases the generic implementation is preferred, so change the polariyon these Kconfig symbols to require architectures to select them whenthey provide their own version.The new name is CONFIG_ARCH_HAS_{STRNCPY_FROM,STRNLEN}_USER.The remaining architectures at the moment are: ia64, mips, parisc,um and xtensa. We should probably convert these as well, butI was not sure how far to take this series. Thomas Bogendoerferhad some concerns about converting mips but may still do somemore detailed measurements to see which version is better.Cc: "James E.J. Bottomley" Cc: Anton Ivanov Cc: Christian Borntraeger Cc: Heiko Carstens Cc: Helge Deller Cc: Jeff Dike Cc: Max Filippov Cc: Richard Weinberger Cc: Thomas Bogendoerfer Cc: Vasily Gorbik Cc: linux-ia64@vger.kernel.orgCc: linux-mips@vger.kernel.orgCc: linux-parisc@vger.kernel.orgCc: linux-s390@vger.kernel.orgCc: linux-um@lists.infradead.orgCc: linux-xtensa@linux-xtensa.orgAcked-by: Geert Uytterhoeven Acked-by: Helge Deller # pariscReviewed-by: Christoph Hellwig Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/nios2/Kconfig

3c188518 - locking/atomic: delete !ARCH_ATOMIC remnants

Tue, 25 May 2021 14:02:31 +0000

locking/atomic: delete !ARCH_ATOMIC remnantsNow that all architectures implement ARCH_ATOMIC, we can make itmandatory, removing the Kconfig symbol and logic for !ARCH_ATOMIC.There should be no functional change as a result of this patch.Signed-off-by: Mark Rutland Acked-by: Geert Uytterhoeven Cc: Boqun Feng Cc: Peter Zijlstra Cc: Will Deacon Signed-off-by: Peter Zijlstra (Intel) Link: https://lore.kernel.org/r/20210525140232.53872-33-mark.rutland@arm.com List of files: /linux-6.15/arch/nios2/Kconfig

7e517b4c - locking/atomic: nios2: move to ARCH_ATOMIC

Tue, 25 May 2021 14:02:23 +0000

locking/atomic: nios2: move to ARCH_ATOMICWe'd like all architectures to convert to ARCH_ATOMIC, as once allarchitectures are converted it will be possible to make significantcleanups to the atomics headers, and this will make it much easier togenerically enable atomic functionality (e.g. debug logic in theinstrumented wrappers).As a step towards that, this patch migrates nios2 to ARCH_ATOMIC, usingthe asm-generic implementations.Signed-off-by: Mark Rutland Cc: Boqun Feng Cc: Ley Foon Tan Cc: Peter Zijlstra Cc: Will Deacon Signed-off-by: Peter Zijlstra (Intel) Link: https://lore.kernel.org/r/20210525140232.53872-25-mark.rutland@arm.com List of files: /linux-6.15/arch/nios2/Kconfig

0774a6ed - timekeeping: default GENERIC_CLOCKEVENTS to enabled

Thu, 24 Sep 2020 09:32:40 +0000

timekeeping: default GENERIC_CLOCKEVENTS to enabledAlmost all machines use GENERIC_CLOCKEVENTS, so it feels wrong torequire each one to select that symbol manually.Instead, enable it whenever CONFIG_LEGACY_TIMER_TICK is disabled asa simplification. It should be possible to select bothGENERIC_CLOCKEVENTS and LEGACY_TIMER_TICK from an architecture nowand decide at runtime between the two.For the clockevents arch-support.txt file, this means that additionalarchitectures are marked as TODO when they have at least one machinethat still uses LEGACY_TIMER_TICK, rather than being marked 'ok' whenat least one machine has been converted. This means that both m68k andarm (for riscpc) revert to TODO.At this point, we could just always enable CONFIG_GENERIC_CLOCKEVENTSrather than leaving it off when not needed. I built an m68kdefconfig kernel (using gcc-10.1.0) and found that this would addaround 5.5KB in kernel image size: text data bss dec hex filename3861936 1092236 196656 5150828 4e986c obj-m68k/vmlinux-no-clockevent3866201 1093832 196184 5156217 4ead79 obj-m68k/vmlinux-clockeventOn Arm (MACH_RPC), that difference appears to be twice as large,around 11KB on top of an 6MB vmlinux.Reviewed-by: Geert Uytterhoeven Acked-by: Geert Uytterhoeven Tested-by: Geert Uytterhoeven Reviewed-by: Linus Walleij Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/nios2/Kconfig

5e6e9852 - uaccess: add infrastructure for kernel builds with set_fs()

Thu, 03 Sep 2020 14:22:35 +0000

uaccess: add infrastructure for kernel builds with set_fs()Add a CONFIG_SET_FS option that is selected by architecturess thatimplement set_fs, which is all of them initially. If the option is notset stubs for routines related to overriding the address space areprovided so that architectures can start to opt out of providing set_fs.Signed-off-by: Christoph Hellwig Reviewed-by: Kees Cook Signed-off-by: Al Viro List of files: /linux-6.15/arch/nios2/Kconfig

140c8180 - arch: remove HAVE_COPY_THREAD_TLS

Sun, 24 May 2020 21:34:20 +0000

arch: remove HAVE_COPY_THREAD_TLSAll architectures support copy_thread_tls() now, so remove the legacycopy_thread() function and the HAVE_COPY_THREAD_TLS config option. Everyoneuses the same process creation calling convention based oncopy_thread_tls() and struct kernel_clone_args. This will make it easier tomaintain the core process creation code under kernel/, simplifies thecallpaths and makes the identical for all architectures.Cc: linux-arch@vger.kernel.orgAcked-by: Thomas Bogendoerfer Acked-by: Greentime Hu Acked-by: Geert Uytterhoeven Reviewed-by: Kees Cook Signed-off-by: Christian Brauner List of files: /linux-6.15/arch/nios2/Kconfig

04bd52fb - nios2: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args

Thu, 07 May 2020 13:14:27 +0000

nios2: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_argsThis is part of a larger series that aims at getting rid of thecopy_thread()/copy_thread_tls() split that makes the process creationcodepaths in the kernel more convoluted and error-prone than they needto be.I'm converting all the remaining arches that haven't yet switched andam collecting individual acks. Once I have them, I'll send the whole seriesremoving the copy_thread()/copy_thread_tls() split, theHAVE_COPY_THREAD_TLS define and the legacy do_fork() helper. The onlykernel-wide process creation entry point for anything not going directlythrough the syscall path will then be based on struct kernel_clone_args.No more danger of weird process creation abi quirks between architectureshopefully, and easier to maintain overall.It also unblocks implementing clone3() on architectures not supportcopy_thread_tls(). Any architecture that wants to implement clone3()will need to select HAVE_COPY_THREAD_TLS and thus need to implementcopy_thread_tls(). So both goals are connected but independentlybeneficial.HAVE_COPY_THREAD_TLS means that a given architecture supportsCLONE_SETTLS and not setting it should usually mean that thearchitectures doesn't implement it but that's not how things are. Infact all architectures support CLONE_TLS it's just that they don'tfollow the calling convention that HAVE_COPY_THREAD_TLS implies. Thatmeans all architectures can be switched over to selectHAVE_COPY_THREAD_TLS. Once that is done we can remove that macro (yay,less code), the unnecessary do_fork() export in kernel/fork.c, and alsorename copy_thread_tls() back to copy_thread(). At this pointcopy_thread() becomes the main architecture specific part of processcreation but it will be the same layout and calling convention for allarchitectures. (Once that is done we can probably cleanup eachcopy_thread() function even more but that's for the future.)Since nios2 does support CLONE_SETTLS there's no reason to not selectHAVE_COPY_THREAD_TLS. This brings us one step closer to getting rid ofthe copy_thread()/copy_thread_tls() split we still have and ultimatelythe HAVE_COPY_THREAD_TLS define in general. A lot of architectures havealready converted and nios2 is one of the few hat haven't yet. This alsounblocks implementing the clone3() syscall on nios2. Once that is done wecan get of another ARCH_WANTS_* macro.Once Any architecture that supports HAVE_COPY_THREAD_TLS cannot call thedo_fork() helper anymore. This is fine and intended since it should beremoved in favor of the new, cleaner _do_fork() calling convention basedon struct kernel_clone_args. In fact, most architectures have alreadyswitched. With this patch, nios2 joins the other arches which can't usethe fork(), vfork(), clone(), clone3() syscalls directly and who followthe new process creation calling convention that is based on structkernel_clone_args which we introduced a while back. This means lesscustom assembly in the architectures entry path to set up the registersbefore calling into the process creation helper and it is easier to tosupport new features without having to adapt calling conventions. Italso unifies all process creation paths between fork(), vfork(),clone(), and clone3(). (We can't fix the ABI nightmare that legacyclone() is but we can prevent stuff like this happening in the future.)For some more context, please see:commit 606e9ad20094f6d500166881d301f31a51bc8aa7Merge: ac61145a725a 457677c70c76Author: Linus Torvalds Date: Sat Jan 11 15:33:48 2020 -0800 Merge tag 'clone3-tls-v5.5-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux Pull thread fixes from Christian Brauner: "This contains a series of patches to fix CLONE_SETTLS when used with clone3(). The clone3() syscall passes the tls argument through struct clone_args instead of a register. This means, all architectures that do not implement copy_thread_tls() but still support CLONE_SETTLS via copy_thread() expecting the tls to be located in a register argument based on clone() are currently unfortunately broken. Their tls value will be garbage. The patch series fixes this on all architectures that currently define __ARCH_WANT_SYS_CLONE3. It also adds a compile-time check to ensure that any architecture that enables clone3() in the future is forced to also implement copy_thread_tls(). My ultimate goal is to get rid of the copy_thread()/copy_thread_tls() split and just have copy_thread_tls() at some point in the not too distant future (Maybe even renaming copy_thread_tls() back to simply copy_thread() once the old function is ripped from all arches). This is dependent now on all arches supporting clone3(). While all relevant arches do that now there are still four missing: ia64, m68k, sh and sparc. They have the system call reserved, but not implemented. Once they all implement clone3() we can get rid of ARCH_WANT_SYS_CLONE3 and HAVE_COPY_THREAD_TLS.Note that in the meantime, m68k has already switched to the new callingconvention. And I've got sparc patches acked by Dave and ia64 is alreadydone too. You can find a link to a booting qemu nios2 system with all thechanges here at [1].[1]: https://asciinema.org/a/333353Cc: linux-kernel@vger.kernel.orgCc: Thomas Gleixner Cc: Sebastian Andrzej Siewior Acked-by: Ley Foon Tan Signed-off-by: Christian Brauner List of files: /linux-6.15/arch/nios2/Kconfig

f26e4331 - arch: nios2: Enable the common clk subsystem on Nios2

Fri, 10 Apr 2020 15:38:23 +0000

arch: nios2: Enable the common clk subsystem on Nios2This patch adds support for common clock framework on Nios2. Clockframework is commonly used in many drivers, and this patch makes itavailable for the entire architecture, not just on a per-driver basis.Signed-off-by: Beniamin Bia Signed-off-by: Dragos Bogdan Signed-off-by: Ley Foon Tan List of files: /linux-6.15/arch/nios2/Kconfig