<?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>0b984652 - powerpc/trace: Account for -fpatchable-function-entry support by toolchain</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#0b984652</link>
        <description>powerpc/trace: Account for -fpatchable-function-entry support by toolchainSo far, we have relied on the fact that gcc supports both-mprofile-kernel, as well as -fpatchable-function-entry, and clangsupports neither. Our Makefile only checks for CONFIG_MPROFILE_KERNEL todecide which files to build. Clang has a feature request out [*] toimplement -fpatchable-function-entry, and is unlikely to support-mprofile-kernel.Update our Makefile checks so that we pick up the correct files to buildonce clang picks up support for -fpatchable-function-entry.[*] https://github.com/llvm/llvm-project/issues/57031Signed-off-by: Naveen N Rao &lt;naveen@kernel.org&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://patch.msgid.link/20241030070850.1361304-2-hbathini@linux.ibm.com

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Wed, 30 Oct 2024 07:08:34 +0000</pubDate>
        <dc:creator>Naveen N Rao &lt;naveen@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>bad90aa5 - powerpc/ftrace: Consolidate ftrace support into fewer files</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#bad90aa5</link>
        <description>powerpc/ftrace: Consolidate ftrace support into fewer filesftrace_low.S has just the _mcount stub and return_to_handler(). Mergethis back into ftrace_mprofile.S and ftrace_64_pg.S to keep all ftracecode together, and to allow those to evolve independently.ftrace_mprofile.S is also not an entirely accurate name since this alsoholds ppc32 code. This will be all the more incorrect once support for-fpatchable-function-entry is added. Rename files here to moreaccurately describe the code:- ftrace_mprofile.S is renamed to ftrace_entry.S- ftrace_pg.c is renamed to ftrace_64_pg.c- ftrace_64_pg.S is rename to ftrace_64_pg_entry.SSigned-off-by: Naveen N Rao &lt;naveen@kernel.org&gt;Reviewed-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://msgid.link/b900c9a8bba9d6c3c295e0f99886acf3e5bf6f7b.1687166935.git.naveen@kernel.org

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Mon, 19 Jun 2023 09:47:25 +0000</pubDate>
        <dc:creator>Naveen N Rao &lt;naveen@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>7f7797b3 - powerpc64/ftrace: Move ELFv1 and -pg support code into a separate file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#7f7797b3</link>
        <description>powerpc64/ftrace: Move ELFv1 and -pg support code into a separate fileELFv1 support is deprecated and on the way out. Pre -mprofile-kernelftrace support (-pg only) is very limited and is retained primarily forclang builds. It won&apos;t be necessary once clang lands support for-fpatchable-function-entry.Copy the existing ftrace code supporting these into ftrace_pg.c.ftrace.c can then be refactored and enhanced with a focus on ppc32 andppc64 ELFv2.Signed-off-by: Naveen N Rao &lt;naveen@kernel.org&gt;Reviewed-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://msgid.link/1eb6cc6c3141ddb77a2a25f8a9e83d83ff312b02.1687166935.git.naveen@kernel.org

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Mon, 19 Jun 2023 09:47:21 +0000</pubDate>
        <dc:creator>Naveen N Rao &lt;naveen@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>2fb857bc - powerpc/kcsan: Add exclusions from instrumentation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#2fb857bc</link>
        <description>powerpc/kcsan: Add exclusions from instrumentationExclude various incompatible compilation units from KCSANinstrumentation.Signed-off-by: Rohan McLure &lt;rmclure@linux.ibm.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20230206021801.105268-2-rmclure@linux.ibm.com

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Mon, 06 Feb 2023 02:17:57 +0000</pubDate>
        <dc:creator>Rohan McLure &lt;rmclure@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>c2cba93d - powerpc/ftrace: Use CONFIG_FUNCTION_TRACER instead of CONFIG_DYNAMIC_FTRACE</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#c2cba93d</link>
        <description>powerpc/ftrace: Use CONFIG_FUNCTION_TRACER instead of CONFIG_DYNAMIC_FTRACESince commit 0c0c52306f47 (&quot;powerpc: Only support DYNAMIC_FTRACE notstatic&quot;), CONFIG_DYNAMIC_FTRACE is always selected whenCONFIG_FUNCTION_TRACER is selected.To avoid confusion and have the reader wonder what&apos;s happen whenCONFIG_FUNCTION_TRACER is selected and CONFIG_DYNAMIC_FTRACE is not,use CONFIG_FUNCTION_TRACER in ifdefs instead of CONFIG_DYNAMIC_FTRACE.As CONFIG_FUNCTION_GRAPH_TRACER depends on CONFIG_FUNCTION_TRACER,ftrace.o doesn&apos;t need to appear for both symbols in Makefile.Then as ftrace.o is built only when CONFIG_FUNCTION_TRACER is selectedifdef CONFIG_FUNCTION_TRACER is not needed in ftrace.c, and since itimplies CONFIG_DYNAMIC_FTRACE, CONFIG_DYNAMIC_FTRACE is not neededin ftrace.cSigned-off-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/628d357503eb90b4a034f99b7df516caaff4d279.1652074503.git.christophe.leroy@csgroup.eu

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Mon, 09 May 2022 05:36:11 +0000</pubDate>
        <dc:creator>Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;</dc:creator>
    </item>
<item>
        <title>a3d0f5b4 - powerpc/ftrace: Don&apos;t include ftrace.o for CONFIG_FTRACE_SYSCALLS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#a3d0f5b4</link>
        <description>powerpc/ftrace: Don&apos;t include ftrace.o for CONFIG_FTRACE_SYSCALLSSince commit 7bea7ac0ca01 (&quot;powerpc/syscalls: Fix syscall tracing&quot;)ftrace.o is not needed anymore for CONFIG_FTRACE_SYSCALLS.Signed-off-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/275932a5d61543b825ff9a64f61abed6da5d4a2a.1652074503.git.christophe.leroy@csgroup.eu

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Mon, 09 May 2022 05:36:10 +0000</pubDate>
        <dc:creator>Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;</dc:creator>
    </item>
<item>
        <title>4ee83a2c - powerpc/ftrace: Remove ftrace_32.S</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#4ee83a2c</link>
        <description>powerpc/ftrace: Remove ftrace_32.SFunctions in ftrace_32.S are common with PPC64.Reuse the ones defined for PPC64 with slight modificationwhen required.Signed-off-by: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;[mpe: Squash in fixup diff from Christophe]Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/5e837fc190504c4ef834272e70d60ae33f175d49.1640017960.git.christophe.leroy@csgroup.eu

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Mon, 20 Dec 2021 16:38:44 +0000</pubDate>
        <dc:creator>Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;</dc:creator>
    </item>
<item>
        <title>fb0b0a73 - powerpc: Enable kcov</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#fb0b0a73</link>
        <description>powerpc: Enable kcovkcov provides kernel coverage data that&apos;s useful for fuzzing tools likesyzkaller.Wire up kcov support on powerpc. Disable kcov instrumentation on the samefiles where we currently disable gcov and UBSan instrumentation, plus someadditional exclusions which appear necessary to boot on book3e machines.Signed-off-by: Andrew Donnellan &lt;andrew.donnellan@au1.ibm.com&gt;Acked-by: Dmitry Vyukov &lt;dvyukov@google.com&gt;Tested-by: Daniel Axtens &lt;dja@axtens.net&gt; # e6500Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Fri, 22 Feb 2019 00:40:46 +0000</pubDate>
        <dc:creator>Andrew Donnellan &lt;andrew.donnellan@au1.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>23ad1a27 - powerpc: Add -Werror at arch/powerpc level</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#23ad1a27</link>
        <description>powerpc: Add -Werror at arch/powerpc levelBack when I added -Werror in commit ba55bd74360e (&quot;powerpc: Addconfigurable -Werror for arch/powerpc&quot;) I did it by adding it to mostof the arch Makefiles.At the time we excluded math-emu, because apparently it didn&apos;t buildcleanly. But that seems to have been fixed somewhere in the interim.So move the -Werror addition to the top-level of the arch, this savesus from repeating it in every Makefile and means we won&apos;t forget toadd it to any new sub-dirs.Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Wed, 10 Oct 2018 05:13:06 +0000</pubDate>
        <dc:creator>Michael Ellerman &lt;mpe@ellerman.id.au&gt;</dc:creator>
    </item>
<item>
        <title>2a056f58 - powerpc: consolidate -mno-sched-epilog into FTRACE flags</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#2a056f58</link>
        <description>powerpc: consolidate -mno-sched-epilog into FTRACE flagsSigned-off-by: Nicholas Piggin &lt;npiggin@gmail.com&gt;Reviewed-by: Joel Stanley &lt;joel@jms.id.au&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Fri, 14 Sep 2018 05:08:53 +0000</pubDate>
        <dc:creator>Nicholas Piggin &lt;npiggin@gmail.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/powerpc/kernel/trace/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/powerpc/kernel/trace/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>096ff2dd - powerpc/ftrace/64: Split further based on -mprofile-kernel</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#096ff2dd</link>
        <description>powerpc/ftrace/64: Split further based on -mprofile-kernelSplit ftrace_64.S further retaining the core ftrace 64-bit aspectsin ftrace_64.S and moving ftrace_caller() and ftrace_graph_caller() intoseparate files based on -mprofile-kernel. The livepatch routines are allnow contained within the mprofile file.Signed-off-by: Naveen N. Rao &lt;naveen.n.rao@linux.vnet.ibm.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Tue, 25 Apr 2017 13:55:54 +0000</pubDate>
        <dc:creator>Naveen N. Rao &lt;naveen.n.rao@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>7853f9c0 - powerpc: Split ftrace bits into a separate file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/powerpc/kernel/trace/Makefile#7853f9c0</link>
        <description>powerpc: Split ftrace bits into a separate fileentry_*.S now includes a lot more than just kernel entry/exit code. As afirst step at cleaning this up, let&apos;s split out the ftrace bits intoseparate files. Also move all related tracing code into a new trace/subdirectory.No functional changes.Suggested-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Signed-off-by: Naveen N. Rao &lt;naveen.n.rao@linux.vnet.ibm.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;

            List of files:
            /linux-6.15/arch/powerpc/kernel/trace/Makefile</description>
        <pubDate>Tue, 25 Apr 2017 13:55:53 +0000</pubDate>
        <dc:creator>Naveen N. Rao &lt;naveen.n.rao@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
</channel>
</rss>
