<?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>ecaf4d3f - kselftest/arm64: Add test coverage for NT_ARM_TLS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/abi/Makefile#ecaf4d3f</link>
        <description>kselftest/arm64: Add test coverage for NT_ARM_TLSIn preparation for extending support for NT_ARM_TLS to cover additionalTPIDRs add some tests for the existing interface. Do this in a genericptrace test program to provide a place to collect additional tests inthe future.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Link: https://lore.kernel.org/r/20220829154921.837871-2-broonie@kernel.orgSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/abi/Makefile</description>
        <pubDate>Mon, 29 Aug 2022 15:49:18 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>7a9bcaaa - kselftest/arm64: Add simple hwcap validation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/abi/Makefile#7a9bcaaa</link>
        <description>kselftest/arm64: Add simple hwcap validationAdd some trivial hwcap validation which checks that /proc/cpuinfo andAT_HWCAP agree with each other and can verify that for extensions that cangenerate a SIGILL due to adding new instructions one appears or doesn&apos;tappear as expected. I&apos;ve added SVE and SME, other capabilities can beadded later if this gets merged.This isn&apos;t super exciting but on the other hand took very little time towrite and should be handy when verifying that you wired up AT_HWCAPproperly.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Link: https://lore.kernel.org/r/20220829154602.827275-1-broonie@kernel.orgSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/abi/Makefile</description>
        <pubDate>Mon, 29 Aug 2022 15:46:02 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>30e3a42b - kselftest/arm64: Add tests for TPIDR2</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/abi/Makefile#30e3a42b</link>
        <description>kselftest/arm64: Add tests for TPIDR2The Scalable Matrix Extension adds a new system register TPIDR2 intended tobe used by libc for its own thread specific use, add some kselftests whichexercise the ABI for it.Since this test should with some adjustment work for TPIDR and any othersimilar registers added in future add tests for it in a separatedirectory rather than placing it with the other floating point tests,nothing existing looked suitable so I created a new test directorycalled &quot;abi&quot;.Since this feature is intended to be used by libc the test is built asfreestanding code using nolibc so we don&apos;t end up with the test programand libc both trying to manage the register simultaneously anddistrupting each other. As a result of being written using nolibc ratherthan using hwcaps to identify if SME is available in the system we checkfor the default SME vector length configuration in proc, adding hwcapsupport to nolibc seems like disproportionate effort and didn&apos;t feelentirely idiomatic for what nolibc is trying to do.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Reviewed-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Link: https://lore.kernel.org/r/20220419112247.711548-31-broonie@kernel.orgSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/abi/Makefile</description>
        <pubDate>Tue, 19 Apr 2022 11:22:38 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b77e995e - kselftest/arm64: Add a test program to exercise the syscall ABI</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/abi/Makefile#b77e995e</link>
        <description>kselftest/arm64: Add a test program to exercise the syscall ABICurrently we don&apos;t have any coverage of the syscall ABI so let&apos;s add a verydumb test program which sets up register patterns, does a sysscall and thenchecks that the register state after the syscall matches what we expect.The program is written in an extremely simplistic fashion with the goal ofmaking it easy to verify that it&apos;s doing what it thinks it&apos;s doing, it isnot a model of how one should write actual code.Currently we validate the general purpose, FPSIMD and SVE registers. Thereare other thing things that could be covered like FPCR and flags registers,these can be covered incrementally - my main focus at the minute iscovering the ABI for the SVE registers.The program repeats the tests for all possible SVE vector lengths in casesome vector length specific optimisation causes issues, as well as testingFPSIMD only. It tries two syscalls, getpid() and sched_yield(), in aneffort to cover both immediate return to userspace and scheduling anothertask though there are no guarantees which cases will be hit.A new test directory &quot;abi&quot; is added to hold the test, it doesn&apos;t seem tofit well into any of the existing directories.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Link: https://lore.kernel.org/r/20211210184133.320748-7-broonie@kernel.orgSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/abi/Makefile</description>
        <pubDate>Fri, 10 Dec 2021 18:41:02 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
