<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Build</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>904708945c07b2b27558b6ffe8923b3df99448f4 - perf test: Compile named_threads workload with -O0</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#904708945c07b2b27558b6ffe8923b3df99448f4</link>
        <description>perf test: Compile named_threads workload with -O0The work loop relies on the compiler not optimizing it away, althoughnamed_threads_work is not static for that reason, the compiler couldstill do it.Fix it by compiling without optimization. Also add -fno-inline forconsistency and in case anyone wants to look at callstacks.Fixes: b5dd510be55e8670 (&quot;perf test: Add named_threads workload&quot;)Closes: https://lore.kernel.org/all/20260609160001.2739E1F00893@smtp.kernel.orgReported-by: sashiko-bot &lt;sashiko-bot@kernel.org&gt;Reviewed-by: Leo Yan &lt;leo.yan@arm.com&gt;Signed-off-by: James Clark &lt;james.clark@linaro.org&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Thu, 11 Jun 2026 13:13:46 +0200</pubDate>
        <dc:creator>James Clark &lt;james.clark@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>2540d48595b9289f1fe6288e080c329a0fd7ce47 - perf test: Add named_threads workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#2540d48595b9289f1fe6288e080c329a0fd7ce47</link>
        <description>perf test: Add named_threads workloadAdd a workload that runs X threads that run a unique function named&quot;named_threads_thread[x]&quot; which performs a multiplication in a loop forY loops. Each thread sets its name to &quot;thread[x]&quot;.This can be used to test that processor trace decoding handlesconcurrent threads correctly and the correct symbols and thread namesare assigned to samples.Signed-off-by: James Clark &lt;james.clark@linaro.org&gt;Cc: Amir Ayupov &lt;aaupov@meta.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: Leo Yan &lt;leo.yan@arm.com&gt;Cc: Mike Leach &lt;mike.leach@arm.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Paschalis Mpeis &lt;Paschalis.Mpeis@arm.com&gt;Cc: Shuah Khan &lt;skhan@linuxfoundation.org&gt;Cc: Suzuki Poulouse &lt;suzuki.poulose@arm.com&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Tue, 09 Jun 2026 16:40:14 +0200</pubDate>
        <dc:creator>James Clark &lt;james.clark@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>3fdf30607e28290d914c44b035f35a9a92512562 - perf test: Add deterministic workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#3fdf30607e28290d914c44b035f35a9a92512562</link>
        <description>perf test: Add deterministic workloadAdd a workload that does the same thing every time for testing CPU tracedecoding.Reviewed-by: Leo Yan &lt;leo.yan@arm.com&gt;Signed-off-by: James Clark &lt;james.clark@linaro.org&gt;Cc: Amir Ayupov &lt;aaupov@meta.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: Mike Leach &lt;mike.leach@arm.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Paschalis Mpeis &lt;Paschalis.Mpeis@arm.com&gt;Cc: Shuah Khan &lt;skhan@linuxfoundation.org&gt;Cc: Suzuki Poulouse &lt;suzuki.poulose@arm.com&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Tue, 09 Jun 2026 16:40:10 +0200</pubDate>
        <dc:creator>James Clark &lt;james.clark@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>4cb5dd0379999af455941ab87d0b30c2ba7d9d66 - perf test: Add a workload that forces context switches</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#4cb5dd0379999af455941ab87d0b30c2ba7d9d66</link>
        <description>perf test: Add a workload that forces context switchesThis workload launches two processes that block when reading and writingto each other forcing the other process to be scheduled for eachread/write pair.Signed-off-by: James Clark &lt;james.clark@linaro.org&gt;Cc: Amir Ayupov &lt;aaupov@meta.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: Leo Yan &lt;leo.yan@arm.com&gt;Cc: Mike Leach &lt;mike.leach@arm.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Paschalis Mpeis &lt;Paschalis.Mpeis@arm.com&gt;Cc: Shuah Khan &lt;skhan@linuxfoundation.org&gt;Cc: Suzuki Poulouse &lt;suzuki.poulose@arm.com&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Tue, 09 Jun 2026 16:40:08 +0200</pubDate>
        <dc:creator>James Clark &lt;james.clark@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>a77ecea7ced2fef7cc0a8ad0323542f781ad9788 - perf test: Remove /usr/bin/cc dependency from Intel PT shell test</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#a77ecea7ced2fef7cc0a8ad0323542f781ad9788</link>
        <description>perf test: Remove /usr/bin/cc dependency from Intel PT shell testIn test_intel_pt.sh, the test script compiled two external C programs atruntime using /usr/bin/cc (a thread loop workload and a JIT self-modifying workload). Relying on external C compilers inside shell testsfrequently causes failures in continuous integration environments.Create a built-in &apos;jitdump&apos; workload and switch test_intel_pt.sh to use&apos;perf test -w thloop&apos; and &apos;perf test -w jitdump&apos;. Also add multi-architecture compatibility without external C compiler dependencies, theworkload instruction arrays dynamically encode CHK_BYTE into opcodesacross x86, ARM32, ARM64, RISC-V, PowerPC, MIPS, LoongArch, and s390x.Some minor include fixes for util/jitdump.h.Assisted-by: Gemini-CLI:Google Gemini 3Signed-off-by: Ian Rogers &lt;irogers@google.com&gt;Tested-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Alexander Shishkin &lt;alexander.shishkin@linux.intel.com&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: James Clark &lt;james.clark@linaro.org&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Tue, 02 Jun 2026 19:41:27 +0200</pubDate>
        <dc:creator>Ian Rogers &lt;irogers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>2e05bb52a12d3cdb81f3b6f5de5cb3905d383552 - perf test workload: Add code_with_type test workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#2e05bb52a12d3cdb81f3b6f5de5cb3905d383552</link>
        <description>perf test workload: Add code_with_type test workloadThe purpose of the workload is to gather samples of rust runtime. Toachieve that it has a dummy rust library linked with it.Per recommendations for such scenarios [1], the rust library isstatically linked.An example:$ perf record perf test -w code_with_type[ perf record: Woken up 1 times to write data ][ perf record: Captured and wrote 0.160 MB perf.data (4074 samples) ]$ perf report --stdio --dso perf -s srcfile,srcline    45.16%  ub_checks.rs       ub_checks.rs:72     6.72%  code_with_type.rs  code_with_type.rs:15     6.64%  range.rs           range.rs:767     4.26%  code_with_type.rs  code_with_type.rs:21     4.23%  range.rs           range.rs:0     3.99%  code_with_type.rs  code_with_type.rs:16    [...][1]: https://doc.rust-lang.org/reference/linkage.html#mixed-rust-and-foreign-codebasesSigned-off-by: Dmitrii Dolgov &lt;9erthalion6@gmail.com&gt;Tested-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Sun, 08 Feb 2026 13:22:24 +0100</pubDate>
        <dc:creator>Dmitrii Dolgov &lt;9erthalion6@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>27fc6f565d06837e71001368c84ee71e5221ce48 - perf test workload: Add inlineloop test workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#27fc6f565d06837e71001368c84ee71e5221ce48</link>
        <description>perf test workload: Add inlineloop test workloadThe purpose of this workload is to gather samples in an inlinedfunction. This can be used to test whether inlined addr2line workscorrectly.Committer testing:  $ perf record perf test -w inlineloop 1  [ perf record: Woken up 2 times to write data ]  [ perf record: Captured and wrote 0.161 MB perf.data (4005 samples) ]  $ perf report --stdio --dso perf -s srcfile,srcline  #  # Total Lost Samples: 0  #  # Samples: 4K of event &apos;cpu/cycles/Pu&apos;  # Event count (approx.): 5535180842  #  # Overhead  Source File   Source:Line  # ........  ............  ...............  #      99.04%  inlineloop.c  inlineloop.c:21       0.46%  inlineloop.c  inlineloop.c:20  #  $Reviewed-by: James Clark &lt;james.clark@linaro.org&gt;Signed-off-by: Ian Rogers &lt;irogers@google.com&gt;Tested-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Alexander Shishkin &lt;alexander.shishkin@linux.intel.com&gt;Cc: Howard Chu &lt;howardchu95@gmail.com&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Stephen Brennan &lt;stephen.s.brennan@oracle.com&gt;Cc: Tony Jones &lt;tonyj@suse.de&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Sun, 11 Jan 2026 05:13:37 +0100</pubDate>
        <dc:creator>Ian Rogers &lt;irogers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>9f0fa213790e3633d37e981386da99149573135b - perf test: Extend branch stack sampling test for Arm64 BRBE</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#9f0fa213790e3633d37e981386da99149573135b</link>
        <description>perf test: Extend branch stack sampling test for Arm64 BRBEBRBE emits IRQ and ERET branches for branching and returning fromtrapped instructions. Add a test that loops on a trapped instruction(MRS - Read special register) for this.Extend the expected &apos;any_call&apos; branches to include FAULT_DATA andFAULT_INST as these are emitted by BRBE.Reviewed-by: Ian Rogers &lt;irogers@google.com&gt;Co-developed-by: German Gomez &lt;german.gomez@arm.com&gt;Signed-off-by: German Gomez &lt;german.gomez@arm.com&gt;Signed-off-by: James Clark &lt;james.clark@linaro.org&gt;Cc: Adam Young &lt;admiyo@os.amperecomputing.com&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Alexander Shishkin &lt;alexander.shishkin@linux.intel.com&gt;Cc: Anshuman Khandual &lt;anshuman.khandual@arm.com&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Mark Rutland &lt;mark.rutland@arm.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Rob Herring &lt;robh@kernel.org&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Wed, 13 Aug 2025 15:38:51 +0200</pubDate>
        <dc:creator>James Clark &lt;james.clark@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>3656e566cf03ab0f959b2bd6f8274ee9799641e6 - perf test: Add landlock workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#3656e566cf03ab0f959b2bd6f8274ee9799641e6</link>
        <description>perf test: Add landlock workloadWe&apos;ll use it to add a regression test for the BTF augmentation of enumarguments for tracepoints in &apos;perf trace&apos;:  root@x1:~# perf trace -e landlock_add_rule perf test -w landlock       0.000 ( 0.009 ms): perf/747160 landlock_add_rule(ruleset_fd: 11, rule_type: LANDLOCK_RULE_PATH_BENEATH, rule_attr: 0x7ffd8e258594, flags: 45) = -1 EINVAL (Invalid argument)       0.011 ( 0.002 ms): perf/747160 landlock_add_rule(ruleset_fd: 11, rule_type: LANDLOCK_RULE_NET_PORT, rule_attr: 0x7ffd8e2585a0, flags: 45) = -1 EINVAL (Invalid argument)  root@x1:~#Committer notes:It was agreed on the discussion (see Link below) to shorten then name ofthe workload from &apos;landlock_add_rule&apos; to &apos;landlock&apos;, and I moved it to aseparate patch.Also, to address a build failure from Namhyung, I stopped loadinglinux/landlock.h and instead added the used defines, enums and types tomake this build in older systems. All we want is to emit the syscall andintercept it.Suggested-by: Arnaldo Carvalho de Melo &lt;acme@kernel.org&gt;Signed-off-by: Howard Chu &lt;howardchu95@gmail.com&gt;Tested-by: Arnaldo Carvalho de Melo &lt;acme@kernel.org&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Kan Liang &lt;kan.liang@linux.intel.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Link: https://lore.kernel.org/lkml/CAH0uvohaypdTV6Z7O5QSK+va_qnhZ6BP6oSJ89s1c1E0CjgxDA@mail.gmail.comLink: https://lore.kernel.org/r/20240624181345.124764-1-howardchu95@gmail.comLink: https://lore.kernel.org/r/20240624181345.124764-6-howardchu95@gmail.comSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Mon, 24 Jun 2024 20:13:42 +0200</pubDate>
        <dc:creator>Howard Chu &lt;howardchu95@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>1dad99af1a8211e2afc1b711c0cda4fbdd445ae2 - perf test: Make tests its own library</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#1dad99af1a8211e2afc1b711c0cda4fbdd445ae2</link>
        <description>perf test: Make tests its own libraryMake the tests code its own library. This is done to avoid compilingcode twice, once for the perf tool and once for the perf pythonmodule.Signed-off-by: Ian Rogers &lt;irogers@google.com&gt;Reviewed-by: James Clark &lt;james.clark@arm.com&gt;Cc: Suzuki K Poulose &lt;suzuki.poulose@arm.com&gt;Cc: Kees Cook &lt;keescook@chromium.org&gt;Cc: Palmer Dabbelt &lt;palmer@dabbelt.com&gt;Cc: Albert Ou &lt;aou@eecs.berkeley.edu&gt;Cc: Nick Terrell &lt;terrelln@fb.com&gt;Cc: Gary Guo &lt;gary@garyguo.net&gt;Cc: Alex Gaynor &lt;alex.gaynor@gmail.com&gt;Cc: Boqun Feng &lt;boqun.feng@gmail.com&gt;Cc: Wedson Almeida Filho &lt;wedsonaf@gmail.com&gt;Cc: Ze Gao &lt;zegao2021@gmail.com&gt;Cc: Alice Ryhl &lt;aliceryhl@google.com&gt;Cc: Andrei Vagin &lt;avagin@google.com&gt;Cc: Yicong Yang &lt;yangyicong@hisilicon.com&gt;Cc: Jonathan Cameron &lt;jonathan.cameron@huawei.com&gt;Cc: Guo Ren &lt;guoren@kernel.org&gt;Cc: Miguel Ojeda &lt;ojeda@kernel.org&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Cc: Mike Leach &lt;mike.leach@linaro.org&gt;Cc: Leo Yan &lt;leo.yan@linux.dev&gt;Cc: Oliver Upton &lt;oliver.upton@linux.dev&gt;Cc: John Garry &lt;john.g.garry@oracle.com&gt;Cc: Benno Lossin &lt;benno.lossin@proton.me&gt;Cc: Bj&#246;rn Roy Baron &lt;bjorn3_gh@protonmail.com&gt;Cc: Andreas Hindborg &lt;a.hindborg@samsung.com&gt;Cc: Paul Walmsley &lt;paul.walmsley@sifive.com&gt;Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Link: https://lore.kernel.org/r/20240625214117.953777-5-irogers@google.com

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Tue, 25 Jun 2024 23:41:13 +0200</pubDate>
        <dc:creator>Ian Rogers &lt;irogers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>3dfc01fe9d12a1e832f49deab37279faa8a9ebc8 - perf test: Add &apos;datasym&apos; test workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#3dfc01fe9d12a1e832f49deab37279faa8a9ebc8</link>
        <description>perf test: Add &apos;datasym&apos; test workloadThe datasym workload is to check if perf mem command gets the dataaddresses precisely.  This is needed for data symbol test.  $ perf test -w datasymI had to keep the buf1 in the data section, otherwise it could endup in the BSS and was mmaped as a separate //anon region, then itwas not symbolized at all.  It needs to be fixed separately.Committer notes:Add a -U _FORTIFY_SOURCE to the datasym CFLAGS, as the main perf flagsset it and it requires building with optimization, and this new test hasa -O0.Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Athira Jajeev &lt;atrajeev@linux.vnet.ibm.com&gt;Cc: German Gomez &lt;german.gomez@arm.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: James Clark &lt;james.clark@arm.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Leo Yan &lt;leo.yan@linaro.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Zhengjun Xing &lt;zhengjun.xing@linux.intel.com&gt;Link: https://lore.kernel.org/r/20221116233854.1596378-12-namhyung@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Thu, 17 Nov 2022 00:38:53 +0100</pubDate>
        <dc:creator>Namhyung Kim &lt;namhyung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>a104f0ea99d846df19aad8a5476eb9bc39fa42ca - perf test: Add &apos;brstack&apos; test workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#a104f0ea99d846df19aad8a5476eb9bc39fa42ca</link>
        <description>perf test: Add &apos;brstack&apos; test workloadThe brstack is to run different kinds of branches repeatedly.  This isnecessary for brstack test case to verify if it has correct branch info.  $ perf test -w brstackI renamed the internal functions to have brstack_ prefix as it&apos;s toogeneric name.Add a -U_FORTIFY_SOURCE to the brstack CFLAGS, as the main perf flagsset it and it requires building with optimization, and this new test hasa -O0.Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Athira Jajeev &lt;atrajeev@linux.vnet.ibm.com&gt;Cc: German Gomez &lt;german.gomez@arm.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: James Clark &lt;james.clark@arm.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Leo Yan &lt;leo.yan@linaro.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Zhengjun Xing &lt;zhengjun.xing@linux.intel.com&gt;Link: https://lore.kernel.org/r/20221116233854.1596378-10-namhyung@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Thu, 17 Nov 2022 00:38:51 +0100</pubDate>
        <dc:creator>Namhyung Kim &lt;namhyung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>39281709a6e2301ac4c6ac7015c7793392ca2dfe - perf test: Add &apos;sqrtloop&apos; test workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#39281709a6e2301ac4c6ac7015c7793392ca2dfe</link>
        <description>perf test: Add &apos;sqrtloop&apos; test workloadThe sqrtloop creates a child process to run an infinite loop callingsqrt() with rand().  This is needed for ARM SPE fork test.  $ perf test -w sqrtloopIt can take an optional argument to specify how long it will run inseconds (default: 1).Committer notes:Explicitely ignored the sqrt() return to fix the build on systems wherethe compiler complains it isn&apos;t being used.And added a sqrtloop specific CFLAGS to disable optimizations to makethis a bit more robust wrt dead code elimination.Doing that a -U_FORTIFY_SOURCE needs to be added, as -O0 is incompatiblewith it.Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Athira Jajeev &lt;atrajeev@linux.vnet.ibm.com&gt;Cc: German Gomez &lt;german.gomez@arm.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: James Clark &lt;james.clark@arm.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Leo Yan &lt;leo.yan@linaro.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Zhengjun Xing &lt;zhengjun.xing@linux.intel.com&gt;Link: https://lore.kernel.org/r/20221116233854.1596378-8-namhyung@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Thu, 17 Nov 2022 00:38:49 +0100</pubDate>
        <dc:creator>Namhyung Kim &lt;namhyung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>41522f7442905814c654dbe2ca7b8d3605c7e0cc - perf test: Add &apos;leafloop&apos; test workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#41522f7442905814c654dbe2ca7b8d3605c7e0cc</link>
        <description>perf test: Add &apos;leafloop&apos; test workloadThe leafloop workload is to run an infinite loop in the test_leaffunction.  This is needed for the ARM fp callgraph test to verify if itgets the correct callchains.  $ perf test -w leafloopCommitter notes:Add a:  -U_FORTIFY_SOURCEto the leafloop CFLAGS as the main perf flags set it and it requiresbuilding with optimization, and this new test has a -O0.Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Athira Jajeev &lt;atrajeev@linux.vnet.ibm.com&gt;Cc: German Gomez &lt;german.gomez@arm.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: James Clark &lt;james.clark@arm.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Leo Yan &lt;leo.yan@linaro.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Zhengjun Xing &lt;zhengjun.xing@linux.intel.com&gt;Link: https://lore.kernel.org/r/20221116233854.1596378-6-namhyung@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Thu, 17 Nov 2022 00:38:47 +0100</pubDate>
        <dc:creator>Namhyung Kim &lt;namhyung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>69b352927885b17f03d3ee4ee38f580699af107a - perf test: Add &apos;thloop&apos; test workload</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#69b352927885b17f03d3ee4ee38f580699af107a</link>
        <description>perf test: Add &apos;thloop&apos; test workloadThe thloop is similar to noploop but runs in two threads.  This isneeded to verify perf record --per-thread to handle multi-threadedprograms properly.  $ perf test -w thloopIt also takes an optional argument to specify runtime in seconds(default: 1).Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Athira Jajeev &lt;atrajeev@linux.vnet.ibm.com&gt;Cc: German Gomez &lt;german.gomez@arm.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: James Clark &lt;james.clark@arm.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Leo Yan &lt;leo.yan@linaro.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Zhengjun Xing &lt;zhengjun.xing@linux.intel.com&gt;Link: https://lore.kernel.org/r/20221116233854.1596378-4-namhyung@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Thu, 17 Nov 2022 00:38:45 +0100</pubDate>
        <dc:creator>Namhyung Kim &lt;namhyung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f215054d749b17c56e014fdca2fcc592dac4529c - perf test: Add -w/--workload option</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/perf/tests/workloads/Build#f215054d749b17c56e014fdca2fcc592dac4529c</link>
        <description>perf test: Add -w/--workload optionThe -w/--workload option is to run a simple workload used by testing.This adds a basic framework to run the workloads and &apos;noploop&apos; workloadas an example.  $ perf test -w noploopThe noploop does a loop doing nothing (NOP) for a second by default.It can have an optional argument to specify the time in seconds.Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Athira Jajeev &lt;atrajeev@linux.vnet.ibm.com&gt;Cc: German Gomez &lt;german.gomez@arm.com&gt;Cc: Ian Rogers &lt;irogers@google.com&gt;Cc: Ingo Molnar &lt;mingo@kernel.org&gt;Cc: James Clark &lt;james.clark@arm.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Leo Yan &lt;leo.yan@linaro.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Zhengjun Xing &lt;zhengjun.xing@linux.intel.com&gt;Link: https://lore.kernel.org/r/20221116233854.1596378-2-namhyung@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/tools/perf/tests/workloads/Build</description>
        <pubDate>Thu, 17 Nov 2022 00:38:43 +0100</pubDate>
        <dc:creator>Namhyung Kim &lt;namhyung@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
