<?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>89d72c03 - kselftest/arm64: Remove spurious comment from MTE test Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#89d72c03</link>
        <description>kselftest/arm64: Remove spurious comment from MTE test MakefileThere&apos;s a stray comment in the MTE test Makefile which documentssomething that&apos;s since been removed, delete it.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Reviewed-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;Link: https://lore.kernel.org/r/20230111-arm64-kselftest-clang-v1-6-89c69d377727@kernel.orgSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Thu, 12 Jan 2023 19:51:52 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>343d5911 - kselftest/arm64: Support build of MTE tests with clang</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#343d5911</link>
        <description>kselftest/arm64: Support build of MTE tests with clangThe assembly portions of the MTE selftests need to be built with atoolchain supporting MTE.  Since we support GCC versions that lack MTEsupport we have logic to suppress build of these tests when using such atoolchain but that logic is broken for LLVM=1 builds, it uses CC but CCis only set for LLVM builds in libs.mk which needs to be included afterwe have selected which test programs to build.Since all supported LLVM versions support MTE we can simply assume MTEsupport when LLVM is set.  This is not a thing of beauty but it does thejob.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Reviewed-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;Link: https://lore.kernel.org/r/20230111-arm64-kselftest-clang-v1-5-89c69d377727@kernel.orgSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Thu, 12 Jan 2023 19:51:51 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>55c8a987 - kselftest/arm64: Don&apos;t enable v8.5 for MTE selftest builds</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#55c8a987</link>
        <description>kselftest/arm64: Don&apos;t enable v8.5 for MTE selftest buildsCurrently we set -march=armv8.5+memtag when building the MTE selftests,allowing the compiler to emit v8.5 and MTE instructions for anything itgenerates. This means that we may get code that will generate SIGILLs whenrun on older systems rather than skipping on non-MTE systems as should bethe case. Most toolchains don&apos;t select any incompatible instructions butI have seen some reports which suggest that some may be appearing which doso. This is also potentially problematic in that if the compiler chooses toemit any MTE instructions for the C code it may interfere with the MTEusage we are trying to test.Since the only reason we are specifying this option is to allow us toassemble MTE instructions in mte_helper.S we can avoid these issues bymoving to using a .arch directive there and adding the -march explicitly tothe toolchain support check instead of the generic CFLAGS.Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt;Link: https://lore.kernel.org/r/20220928154517.173108-1-broonie@kernel.orgSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Wed, 28 Sep 2022 15:45:17 +0000</pubDate>
        <dc:creator>Mark Brown &lt;broonie@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f2745dc0 - selftests: stop using KSFT_KHDR_INSTALL</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#f2745dc0</link>
        <description>selftests: stop using KSFT_KHDR_INSTALLStop using the KSFT_KHDR_INSTALL flag as installing the kernel headersfrom the kselftest Makefile is causing some issues.  Instead, rely onthe headers to be installed directly by the top-level Makefile&quot;headers_install&quot; make target prior to building kselftest.Signed-off-by: Guillaume Tucker &lt;guillaume.tucker@collabora.com&gt;Tested-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Fri, 08 Jul 2022 16:23:28 +0000</pubDate>
        <dc:creator>Guillaume Tucker &lt;guillaume.tucker@collabora.com&gt;</dc:creator>
    </item>
<item>
        <title>9466ecac - kselftest/arm64: mte: Makefile: Fix clang compilation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#9466ecac</link>
        <description>kselftest/arm64: mte: Makefile: Fix clang compilationWhen clang finds a header file on the command line, it wants toprecompile that, which would end up in a separate output file.Specifying -o on that same command line collides with that effort, sothe compiler complains:clang: error: cannot specify -o when generating multiple output filesSince we are not really after a precompiled header, just drop the headerfile from the command line, by removing it from the list of sourcefiles in the Makefile.Signed-off-by: Andre Przywara &lt;andre.przywara@arm.com&gt;Reviewed-by: Mark Brown &lt;broone@kernel.org&gt;Link: https://lore.kernel.org/r/20210319165334.29213-10-andre.przywara@arm.comSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Fri, 19 Mar 2021 16:53:32 +0000</pubDate>
        <dc:creator>Andre Przywara &lt;andre.przywara@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>8bbb58a3 - kselftest/arm64: mte: Output warning about failing compiler</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#8bbb58a3</link>
        <description>kselftest/arm64: mte: Output warning about failing compilerAt the moment we check the compiler&apos;s ability to compile MTE enabledcode, but guard all the Makefile rules by it. As a consequence a brokenor not capable compiler just doesn&apos;t do anything, and make happilyreturns without any error message, but with no programs created.Since the MTE feature is only supported by recent aarch64 compilers (notall stable distro compilers support it), having an explicit messageseems like a good idea. To not break building multiple targets, we letmake proceed without errors.Signed-off-by: Andre Przywara &lt;andre.przywara@arm.com&gt;Reviewed-by: Mark Brown &lt;broone@kernel.org&gt;Link: https://lore.kernel.org/r/20210319165334.29213-9-andre.przywara@arm.comSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Fri, 19 Mar 2021 16:53:31 +0000</pubDate>
        <dc:creator>Andre Przywara &lt;andre.przywara@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>5238c2cd - kselftest/arm64: mte: Use cross-compiler if specified</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#5238c2cd</link>
        <description>kselftest/arm64: mte: Use cross-compiler if specifiedAt the moment we either need to provide CC explicitly, or use a nativemachine to get the ARM64 MTE selftest compiled.It seems useful to use the same (cross-)compiler as we use for thekernel, so copy the recipe we use in the pauth selftest.Signed-off-by: Andre Przywara &lt;andre.przywara@arm.com&gt;Reviewed-by: Mark Brown &lt;broone@kernel.org&gt;Link: https://lore.kernel.org/r/20210319165334.29213-8-andre.przywara@arm.comSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Fri, 19 Mar 2021 16:53:30 +0000</pubDate>
        <dc:creator>Andre Przywara &lt;andre.przywara@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>e5decefd - kselftest/arm64: mte: Fix pthread linking</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#e5decefd</link>
        <description>kselftest/arm64: mte: Fix pthread linkingThe GCC manual suggests to use -pthread, when linking with the PThreadlibrary, also to add this switch to both the compilation and linkingstages.Do as the manual says, to fix compilation with Ubuntu&apos;s 20.04 toolchain,which was getting -lpthread too early on the command line:------------/usr/bin/ld: /tmp/cc5zbo2A.o: in function `execute_test&apos;:tools/testing/selftests/arm64/mte/check_gcr_el1_cswitch.c:86:	undefined reference to `pthread_create&apos;/usr/bin/ld: tools/testing/selftests/arm64/mte/check_gcr_el1_cswitch.c:90:	undefined reference to `pthread_join&apos;------------Signed-off-by: Andre Przywara &lt;andre.przywara@arm.com&gt;Reviewed-by: Mark Brown &lt;broone@kernel.org&gt;Link: https://lore.kernel.org/r/20210319165334.29213-3-andre.przywara@arm.comSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Fri, 19 Mar 2021 16:53:25 +0000</pubDate>
        <dc:creator>Andre Przywara &lt;andre.przywara@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>4a423645 - kselftest/arm64: mte: Fix compilation with native compiler</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#4a423645</link>
        <description>kselftest/arm64: mte: Fix compilation with native compilerThe mte selftest Makefile contains a check for GCC, to add the memtag-march flag to the compiler options. This check fails if the compileris not explicitly specified, so reverts to the standard &quot;cc&quot;, in whichcase --version doesn&apos;t mention the &quot;gcc&quot; string we match against:$ cc --version | head -n 1cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0This will not add the -march switch to the command line, so compilationfails:mte_helper.S: Assembler messages:mte_helper.S:25: Error: selected processor does not support `irg x0,x0,xzr&apos;mte_helper.S:38: Error: selected processor does not support `gmi x1,x0,xzr&apos;...Actually clang accepts the same -march option as well, so we can justdrop this check and add this unconditionally to the command line, to avoidany future issues with this check altogether (gcc actually printsbasename(argv[0]) when called with --version).Signed-off-by: Andre Przywara &lt;andre.przywara@arm.com&gt;Reviewed-by: Nick Desaulniers &lt;ndesaulniers@google.com&gt;Reviewed-by: Mark Brown &lt;broone@kernel.org&gt;Link: https://lore.kernel.org/r/20210319165334.29213-2-andre.przywara@arm.comSigned-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Fri, 19 Mar 2021 16:53:24 +0000</pubDate>
        <dc:creator>Andre Przywara &lt;andre.przywara@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>29f08088 - kselftest/arm64: check GCR_EL1 after context switch</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#29f08088</link>
        <description>kselftest/arm64: check GCR_EL1 after context switchThis test is specific to MTE and verifies that the GCR_EL1 register iscontext switched correctly.It spawns 1024 processes and each process spawns 5 threads.  Each threadwrites a random setting of GCR_EL1 through the prctl() system call andreads it back verifying that it is the same.  If the values are not thesame it reports a failure.Note: The test has been extended to verify that even SYNC and ASYNC modesetting is preserved correctly over context switching.Link: https://lkml.kernel.org/r/b51a165426e906e7ec8a68d806ef3f8cd92581a6.1606161801.git.andreyknvl@google.comSigned-off-by: Vincenzo Frascino &lt;vincenzo.frascino@arm.com&gt;Signed-off-by: Andrey Konovalov &lt;andreyknvl@google.com&gt;Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Tested-by: Vincenzo Frascino &lt;vincenzo.frascino@arm.com&gt;Cc: Alexander Potapenko &lt;glider@google.com&gt;Cc: Andrey Ryabinin &lt;aryabinin@virtuozzo.com&gt;Cc: Branislav Rankov &lt;Branislav.Rankov@arm.com&gt;Cc: Dmitry Vyukov &lt;dvyukov@google.com&gt;Cc: Evgenii Stepanov &lt;eugenis@google.com&gt;Cc: Kevin Brodsky &lt;kevin.brodsky@arm.com&gt;Cc: Marco Elver &lt;elver@google.com&gt;Cc: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Cc: Will Deacon &lt;will.deacon@arm.com&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Tue, 22 Dec 2020 20:02:27 +0000</pubDate>
        <dc:creator>Vincenzo Frascino &lt;vincenzo.frascino@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>e9b60476 - kselftest/arm64: Add utilities and a test to validate mte memory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/arm64/mte/Makefile#e9b60476</link>
        <description>kselftest/arm64: Add utilities and a test to validate mte memoryThis test checks that the memory tag is present after mte allocation andthe memory is accessible with those tags. This testcase verifies allsync, async and none mte error reporting mode. The allocated mte buffersare verified for Allocated range (no error expected while accessingbuffer), Underflow range, and Overflow range.Different test scenarios covered here are,* Verify that mte memory are accessible at byte/block level.* Force underflow and overflow to occur and check the data consistency.* Check to/from between tagged and untagged memory.* Check that initial allocated memory to have 0 tag.This change also creates the necessary infrastructure to add mte testcases. MTE kselftests can use the several utility functions provided hereto add wide variety of mte test scenarios.GCC compiler need flag &apos;-march=armv8.5-a+memtag&apos; so those flags areverified before compilation.The mte testcases can be launched with kselftest framework as,make TARGETS=arm64 ARM64_SUBTARGETS=mte kselftestor compiled as,make -C tools/testing/selftests TARGETS=arm64 ARM64_SUBTARGETS=mte CC=&apos;compiler&apos;Co-developed-by: Gabor Kertesz &lt;gabor.kertesz@arm.com&gt;Signed-off-by: Gabor Kertesz &lt;gabor.kertesz@arm.com&gt;Signed-off-by: Amit Daniel Kachhap &lt;amit.kachhap@arm.com&gt;Tested-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Cc: Shuah Khan &lt;shuah@kernel.org&gt;Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Link: https://lore.kernel.org/r/20201002115630.24683-2-amit.kachhap@arm.comSigned-off-by: Will Deacon &lt;will@kernel.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/arm64/mte/Makefile</description>
        <pubDate>Fri, 02 Oct 2020 11:56:25 +0000</pubDate>
        <dc:creator>Amit Daniel Kachhap &lt;amit.kachhap@arm.com&gt;</dc:creator>
    </item>
</channel>
</rss>
