<?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>108e5e68 - selftests/powerpc: make sub-folders buildable on their own</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/powerpc/eeh/Makefile#108e5e68</link>
        <description>selftests/powerpc: make sub-folders buildable on their ownBuild breaks when executing make with run_tests for sub-foldersunder powerpc. This is because, CFLAGS and GIT_VERSION macros aredefined in Makefile of toplevel powerpc folder.  make: Entering directory &apos;/home/maddy/linux/tools/testing/selftests/powerpc/mm&apos;  gcc     hugetlb_vs_thp_test.c ../harness.c ../utils.c  -o /home/maddy/selftest_output//hugetlb_vs_thp_test  hugetlb_vs_thp_test.c:6:10: fatal error: utils.h: No such file or directory      6 | #include &quot;utils.h&quot;        |          ^~~~~~~~~  compilation terminated.Fix this by adding the flags.mk in each sub-folder Makefile. Also removethe CFLAGS and GIT_VERSION macros from powerpc/ folder Makefile sincethe same is definied in flags.mkSigned-off-by: Madhavan Srinivasan &lt;maddy@linux.ibm.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://msgid.link/20240229093711.581230-3-maddy@linux.ibm.com

            List of files:
            /linux-6.15/tools/testing/selftests/powerpc/eeh/Makefile</description>
        <pubDate>Thu, 29 Feb 2024 09:37:11 +0000</pubDate>
        <dc:creator>Madhavan Srinivasan &lt;maddy@linux.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>f5eca0b2 - selftests/powerpc/eeh: disable kselftest timeout setting for eeh-basic</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/powerpc/eeh/Makefile#f5eca0b2</link>
        <description>selftests/powerpc/eeh: disable kselftest timeout setting for eeh-basicThe eeh-basic test got its own 60 seconds timeout (defined in commit414f50434aa2 &quot;selftests/eeh: Bump EEH wait time to 60s&quot;) per breakabledevice.And we have discovered that the number of breakable devices varieson different hardware. The device recovery time ranges from 0 to 35seconds. In our test pool it will take about 30 seconds to run on aPower8 system that with 5 breakable devices, 60 seconds to run on aPower9 system that with 4 breakable devices.Extend the timeout setting in the kselftest framework to 5 minutesto give it a chance to finish.Signed-off-by: Po-Hsu Lin &lt;po-hsu.lin@canonical.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20201023024539.9512-1-po-hsu.lin@canonical.com

            List of files:
            /linux-6.15/tools/testing/selftests/powerpc/eeh/Makefile</description>
        <pubDate>Fri, 23 Oct 2020 02:45:39 +0000</pubDate>
        <dc:creator>Po-Hsu Lin &lt;po-hsu.lin@canonical.com&gt;</dc:creator>
    </item>
<item>
        <title>85d86c8a - selftests/powerpc: Add basic EEH selftest</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/powerpc/eeh/Makefile#85d86c8a</link>
        <description>selftests/powerpc: Add basic EEH selftestUse the new eeh_dev_check and eeh_dev_break interfaces to test EEHrecovery.  Historically this has been done manually using platform specificEEH error injection facilities (e.g. via RTAS). However, documentation onhow to use these facilities is haphazard at best and non-existent at worstso it&apos;s hard to develop a cross-platform test.The new debugfs interfaces allow the kernel to handle the platform specificdetails so we can write a more generic set of sets. This patch adds themost basic of recovery tests where:a) Errors are injected and recovered from sequentially,b) Errors are not injected into PCI-PCI bridges, such as PCIe switches.c) Errors are only injected into device function zero.d) No errors are injected into Virtual Functions.a), b) and c) are largely due to limitations of Linux&apos;s EEH support.  EEHrecovery is serialised in the EEH recovery thread which forces a).Similarly, multi-function PCI devices are almost always grouped into thesame PE so injecting an error on one function exercises the same codepaths. c) is because we currently more or less ignore PCI bridges duringrecovery and assume that the recovered topology will be the same as theoriginal.d) is due to the limits of the eeh_dev_break interface. With the currentimplementation we can&apos;t inject an error into a specific VF withoutpotentially causing additional errors on other VFs. Due to the serialisedrecovery process we might end up timing out waiting for another function torecover before the function of interest is recovered. The platform specificerror injection facilities are finer-grained and allow this capability, butdoing that requires working out how to use those facilities first.Basicly, it&apos;s better than nothing and it&apos;s a base to build on.Signed-off-by: Oliver O&apos;Halloran &lt;oohall@gmail.com&gt;Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Link: https://lore.kernel.org/r/20190903101605.2890-15-oohall@gmail.com

            List of files:
            /linux-6.15/tools/testing/selftests/powerpc/eeh/Makefile</description>
        <pubDate>Tue, 03 Sep 2019 10:16:05 +0000</pubDate>
        <dc:creator>Oliver O&apos;Halloran &lt;oohall@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
