<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>00807191 - s390/crc32: expose CRC32 functions through lib</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#00807191</link>
        <description>s390/crc32: expose CRC32 functions through libMove the s390 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 &quot;shash&quot; code becomes unnecessary and is removed.Note: to see the diff from arch/s390/crypto/crc32-vx.c toarch/s390/lib/crc32-glue.c, view this commit with &apos;git show -M10&apos;.Reviewed-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;Link: https://lore.kernel.org/r/20241202010844.144356-10-ebiggers@kernel.orgSigned-off-by: Eric Biggers &lt;ebiggers@google.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Mon, 02 Dec 2024 01:08:34 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>ba05b39d - s390/expoline: Make modules use kernel expolines</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#ba05b39d</link>
        <description>s390/expoline: Make modules use kernel expolinesCurrently, kernel modules contain their own set of expoline thunks. Inthe case of EXPOLINE_EXTERN, this involves postlinking of precompiledexpoline.o. expoline.o is also necessary for out-of-source tree modulebuilds.Now that the kernel modules area is less than 4 GB away fromkernel expoline thunks, make modules use kernel expolines. Also makeEXPOLINE_EXTERN the default if the compiler supports it. This simplifiesbuild and aligns with the approach adopted by other architectures.Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Signed-off-by: Alexander Gordeev &lt;agordeev@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Wed, 17 Jan 2024 10:50:49 +0000</pubDate>
        <dc:creator>Vasily Gorbik &lt;gor@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>cb2a1dd5 - s390/checksum: provide vector register variant of csum_partial()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#cb2a1dd5</link>
        <description>s390/checksum: provide vector register variant of csum_partial()Provide a faster variant of csum_partial() which uses vector registersinstead of the cksm instruction.Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Sat, 03 Feb 2024 10:45:22 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;hca@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>fbac266f - s390: select ARCH_SUPPORTS_INT128</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#fbac266f</link>
        <description>s390: select ARCH_SUPPORTS_INT128s390 has instructions to support 128 bit arithmetics, e.g. a 64 bitmultiply instruction with a 128 bit result. Also 128 bit integerartithmetics are already used in s390 specific architecture code (seee.g. read_persistent_clock64()).Therefore select ARCH_SUPPORTS_INT128.However limit this to clang for now, since gcc generates inefficient code,which may lead to stack overflows, when compilinglib/crypto/curve25519-hacl64.c which depends on ARCH_SUPPORTS_INT128. Thegcc generated functions have 6kb stack frames, compared to only 1kb of thecode generated with clang.If the kernel is compiled with -Os library calls for __ashlti3(),__ashrti3(), and __lshrti3() may be generated. Similar to arm64and riscv provide assembler implementations for these functions.Acked-by: Alexander Gordeev &lt;agordeev@linux.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;Signed-off-by: Alexander Gordeev &lt;agordeev@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Tue, 25 Apr 2023 11:42:11 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;hca@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>c4e78957 - s390/nospec: build expoline.o for modules_prepare target</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#c4e78957</link>
        <description>s390/nospec: build expoline.o for modules_prepare targetWhen CONFIG_EXPOLINE_EXTERN is used expoline thunks are generatedfrom arch/s390/lib/expoline.S and postlinked into every module.This is also true for external modules. Add expoline.o build tothe modules_prepare target.Fixes: 1d2ad084800e (&quot;s390/nospec: add an option to use thunk-extern&quot;)Reported-by: Joe Lawrence &lt;joe.lawrence@redhat.com&gt;Tested-by: Sumanth Korikkar &lt;sumanthk@linux.ibm.com&gt;Acked-by: Sumanth Korikkar &lt;sumanthk@linux.ibm.com&gt;Tested-by: C. Erastus Toe &lt;ctoe@redhat.com&gt;Tested-by: Joe Lawrence &lt;joe.lawrence@redhat.com&gt;Link: https://lore.kernel.org/r/patch-1.thread-d13b6c.git-a2387a74dc49.your-ad-here.call-01656331067-ext-4899@work.hoursSigned-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Signed-off-by: Alexander Gordeev &lt;agordeev@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Mon, 27 Jun 2022 12:50:53 +0000</pubDate>
        <dc:creator>Vasily Gorbik &lt;gor@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>1d2ad084 - s390/nospec: add an option to use thunk-extern</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#1d2ad084</link>
        <description>s390/nospec: add an option to use thunk-externCurrently with -mindirect-branch=thunk and -mfunction-return=thunk compileroptions expoline thunks are put into individual COMDAT group sections. s390is the only architecture which has group sections and it has implicationsfor kpatch and objtool tools support.Using -mindirect-branch=thunk-extern and -mfunction-return=thunk-externis an alternative, which comes with a need to generate all requiredexpoline thunks manually. Unfortunately modules area is too far away fromthe kernel image, and expolines from the kernel image cannon be used.But since all new distributions (except Debian) build kernels for machinegenerations newer than z10, where &quot;exrl&quot; instruction is available, thatleaves only 16 expolines thunks possible.Provide an option to build the kernel with-mindirect-branch=thunk-extern and -mfunction-return=thunk-extern forz10 or newer. This also requires to postlink expoline thunks into allmodules explicitly. Currently modules already contain most expolinesanyhow.Unfortunately -mindirect-branch=thunk-extern and-mfunction-return=thunk-extern options support is broken in gcc &lt;= 11.2.Additional compile test is required to verify proper gcc support.Acked-by: Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;Co-developed-by: Sumanth Korikkar &lt;sumanthk@linux.ibm.com&gt;Signed-off-by: Sumanth Korikkar &lt;sumanthk@linux.ibm.com&gt;Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Sun, 06 Mar 2022 19:56:07 +0000</pubDate>
        <dc:creator>Vasily Gorbik &lt;gor@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>90c53187 - s390/module: test loading modules with a lot of relocations</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#90c53187</link>
        <description>s390/module: test loading modules with a lot of relocationsAdd a test in order to prevent regressions.Signed-off-by: Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;Reviewed-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;Cc: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Cc: Christian Borntraeger &lt;borntraeger@linux.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Wed, 19 Jan 2022 18:26:38 +0000</pubDate>
        <dc:creator>Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>d340d28a - kprobes: add testcases for s390</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#d340d28a</link>
        <description>kprobes: add testcases for s390Add a few testcases to make sure that it&apos;s not possible to placea kprobe in the mid of an instruction on s390.Signed-off-by: Sven Schnelle &lt;svens@linux.ibm.com&gt;Acked-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Thu, 09 Sep 2021 18:59:17 +0000</pubDate>
        <dc:creator>Sven Schnelle &lt;svens@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>73d6eb48 - s390: enable HAVE_FUNCTION_ERROR_INJECTION</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#73d6eb48</link>
        <description>s390: enable HAVE_FUNCTION_ERROR_INJECTIONThis kernel feature is required for enabling BPF_KPROBE_OVERRIDE.Define override_function_with_return() and regs_set_return_value()functions, and fix compile errors in syscall_wrapper.h.Signed-off-by: Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;hca@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Wed, 22 Jul 2020 21:58:54 +0000</pubDate>
        <dc:creator>Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>badbf397 - s390/unwind: add a test for the internal API</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#badbf397</link>
        <description>s390/unwind: add a test for the internal APIunwind_for_each_frame can take at least 8 different sets of parameters.Add a test to make sure they all are handled in a sane way.Reviewed-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;Co-developed-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Thu, 17 Oct 2019 13:09:08 +0000</pubDate>
        <dc:creator>Ilya Leoshkevich &lt;iii@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>2e83e0eb - s390: clean .bss before running uncompressed kernel</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#2e83e0eb</link>
        <description>s390: clean .bss before running uncompressed kernelClean uncompressed kernel .bss section in the startup code beforethe uncompressed kernel is executed. At this point of time initrd andcertificates have been already rescued. Uncompressed kernel .bss sizeis known from vmlinux_info. It is also taken into consideration duringuncompressed kernel positioning by kaslr (so it is safe to clean it).With that uncompressed kernel is starting with .bss section zeroed andno .bss section usage restrictions apply. Which makes chkbss checks foruncompressed kernel objects obsolete and they can be removed.early_nobss.c is also not needed anymore. Parts of it which are stillrelevant are moved to early.c. Kasan initialization code is now calleddirectly from head64 (early.c is instrumented and should not beexecuted before kasan shadow memory is set up).Reviewed-by: Philipp Rudo &lt;prudo@linux.ibm.com&gt;Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Sun, 11 Aug 2019 18:55:18 +0000</pubDate>
        <dc:creator>Vasily Gorbik &lt;gor@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>67626fad - s390: enforce CONFIG_SMP</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#67626fad</link>
        <description>s390: enforce CONFIG_SMPThere never have been distributions that shiped with CONFIG_SMP=n fors390. In addition the kernel currently doesn&apos;t even compile withCONFIG_SMP=n for s390. Most likely it wouldn&apos;t even work, even if wefix the compile error, since nobody tests it, since there is no usecase that I can think of.Therefore simply enforce CONFIG_SMP and get rid of some more orless unused code.Reviewed-by: Christian Borntraeger &lt;borntraeger@de.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Mon, 03 Jun 2019 12:25:18 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>b6cbe3e8 - s390/kasan: avoid user access code instrumentation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#b6cbe3e8</link>
        <description>s390/kasan: avoid user access code instrumentationKasan instrumentation adds &quot;store&quot; check for variables marked asmodified by inline assembly. With user pointers containing addressesfrom another address space this produces false positives.static inline unsigned long clear_user_xc(void __user *to, ...){	asm volatile(	...	: &quot;+a&quot; (to) ...User space access functions are wrapped by manually instrumentedfunctions in kasan common code, which should be sufficient to catcherrors. So, we just disable uaccess.o instrumentation altogether.Reviewed-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Fri, 17 Nov 2017 16:20:28 +0000</pubDate>
        <dc:creator>Vasily Gorbik &lt;gor@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>0391fcb5 - s390: introduce compile time check for empty .bss section</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#0391fcb5</link>
        <description>s390: introduce compile time check for empty .bss sectionIntroduce compile time check for files which should avoid using .bsssection, because of the following reasons:- .bss section has not been zeroed yet,- initrd has not been moved to a safe location and could be overlappingwith .bss section.Reviewed-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Thu, 03 May 2018 14:40:13 +0000</pubDate>
        <dc:creator>Vasily Gorbik &lt;gor@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#b2441318</link>
        <description>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 &apos;GPL-2.0&apos;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 &amp; 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 &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;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 &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  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&apos;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 &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>2cfc5f9c - s390/xor: optimized xor routing using the XC instruction</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#2cfc5f9c</link>
        <description>s390/xor: optimized xor routing using the XC instructionAcked-by: Christian Borntraeger &lt;borntraeger@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Tue, 02 Feb 2016 13:40:40 +0000</pubDate>
        <dc:creator>Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>304987e3 - s390: remove &quot;64&quot; suffix from mem64.S and swsusp_asm64.S</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#304987e3</link>
        <description>s390: remove &quot;64&quot; suffix from mem64.S and swsusp_asm64.SRename two more files which I forgot. Also remove the &quot;asm&quot; from theswsusp_asm64.S file, since the &quot;.S&quot; suffix already makes it obviousthat this file contains assembler code.Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Tue, 24 Mar 2015 07:10:53 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>5a79859a - s390: remove 31 bit support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#5a79859a</link>
        <description>s390: remove 31 bit supportRemove the 31 bit support in order to reduce maintenance cost andeffectively remove dead code. Since a couple of years there is nodistribution left that comes with a 31 bit kernel.The 31 bit kernel also has been broken since more than a year beforeanybody noticed. In addition I added a removal warning to the kernelshown at ipl for 5 minutes: a960062e5826 (&quot;s390: add 31 bit warningmessage&quot;) which let everybody know about the plan to remove 31 bitcode. We didn&apos;t get any response.Given that the last 31 bit only machine was introduced in 1999 let&apos;sremove the code.Anybody with 31 bit user space code can still use the compat mode.Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Thu, 12 Feb 2015 12:08:27 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>975fab17 - s390/uprobes: common library for kprobes and uprobes</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#975fab17</link>
        <description>s390/uprobes: common library for kprobes and uprobesThis patch moves common functions from kprobes.c to probes.c.Thus its possible for uprobes to use them without enabling kprobes.Signed-off-by: Jan Willeke &lt;willeke@de.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Mon, 22 Sep 2014 14:37:27 +0000</pubDate>
        <dc:creator>Jan Willeke &lt;willeke@de.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>457f2180 - s390/uaccess: rework uaccess code - fix locking issues</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/s390/lib/Makefile#457f2180</link>
        <description>s390/uaccess: rework uaccess code - fix locking issuesThe current uaccess code uses a page table walk in some circumstances,e.g. in case of the in atomic futex operations or if running on oldhardware which doesn&apos;t support the mvcos instruction.However it turned out that the page table walk code does not correctlylock page tables when accessing page table entries.In other words: a different cpu may invalidate a page table entry whilethe current cpu inspects the pte. This may lead to random data corruption.Adding correct locking however isn&apos;t trivial for all uaccess operations.Especially copy_in_user() is problematic since that requires to hold atleast two locks, but must be protected against ABBA deadlock when adifferent cpu also performs a copy_in_user() operation.So the solution is a different approach where we change address spaces:User space runs in primary address mode, or access register mode withinvdso code, like it currently already does.The kernel usually also runs in home space mode, however when accessinguser space the kernel switches to primary or secondary address mode ifthe mvcos instruction is not available or if a compare-and-swap (futex)instruction on a user space address is performed.KVM however is special, since that requires the kernel to run in homeaddress space while implicitly accessing user space with the sieinstruction.So we end up with:User space:- runs in primary or access register mode- cr1 contains the user asce- cr7 contains the user asce- cr13 contains the kernel asceKernel space:- runs in home space mode- cr1 contains the user or kernel asce  -&gt; the kernel asce is loaded when a uaccess requires primary or     secondary address mode- cr7 contains the user or kernel asce, (changed with set_fs())- cr13 contains the kernel asceIn case of uaccess the kernel changes to:- primary space mode in case of a uaccess (copy_to_user) and uses  e.g. the mvcp instruction to access user space. However the kernel  will stay in home space mode if the mvcos instruction is available- secondary space mode in case of futex atomic operations, so that the  instructions come from primary address space and data from secondary  spaceIn case of kvm the kernel runs in home space mode, but cr1 gets switchedto contain the gmap asce before the sie instruction gets executed. Whenthe sie instruction is finished cr1 will be switched back to contain theuser asce.A context switch between two processes will always load the kernel ascefor the next process in cr1. So the first exit to user space is a bitmore expensive (one extra load control register instruction) than before,however keeps the code rather simple.In sum this means there is no need to perform any error prone page tablewalks anymore when accessing user space.The patch seems to be rather large, however it mainly removes thethe page table walk code and restores the previously deleted &quot;standard&quot;uaccess code, with a couple of changes.The uaccess without mvcos mode can be enforced with the &quot;uaccess_primary&quot;kernel parameter.Reported-by: Christian Borntraeger &lt;borntraeger@de.ibm.com&gt;Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;

            List of files:
            /linux-6.15/arch/s390/lib/Makefile</description>
        <pubDate>Fri, 21 Mar 2014 09:42:25 +0000</pubDate>
        <dc:creator>Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;</dc:creator>
    </item>
</channel>
</rss>
