From: James Clark <james.clark@linaro.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>, Leo Yan <leo.yan@arm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf test: Compile named_threads workload with -O0
Date: Fri, 12 Jun 2026 09:24:29 +0100 [thread overview]
Message-ID: <453d71dc-1bd1-40e0-81e4-c578f64f438c@linaro.org> (raw)
In-Reply-To: <20260611195449.7230e316@pumpkin>
On 11/06/2026 7:54 pm, David Laight wrote:
> On Thu, 11 Jun 2026 12:13:46 +0100
> James Clark <james.clark@linaro.org> wrote:
>
>> The work loop relies on the compiler not optimizing it away, although
>> named_threads_work is not static for that reason, the compiler could
>> still do it.
>
> Isn't in enough to put barrier() in the loop?
>
> David
>
Probably, but I don't think it would make a difference for this specific
test workload, and I don't think that style has ever been used for any
of the Perf tests.
I think Sashiko's comment leading to this was overly pedantic, neither
GCC or Clang optimize this away even with -O2. So in this specific case
it was only fixing a hypothetical which is why I didn't add a fixes tag.
Although I admit there is some chance it could happen with other changes.
However, I think -O0 is the appropriate fix for a workload because it
makes the stacks and order of execution predictable, which is what the
tests look at. And that also has the effect of guaranteeing this isn't
optimized away, so we probably don't need both.
Thanks
James
>>
>> Fix it by compiling without optimization. Also add -fno-inline for
>> consistency and in case anyone wants to look at callstacks.
>>
>> Signed-off-by: James Clark <james.clark@linaro.org>
>> ---
>> One trailing Sashiko fix from the "perf cs-etm: Queue context packets
>> for frontend" patch series that has been applied already.
>> ---
>> tools/perf/tests/workloads/Build | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/perf/tests/workloads/Build b/tools/perf/tests/workloads/Build
>> index 75b377934a0e..7bb4b9829ba2 100644
>> --- a/tools/perf/tests/workloads/Build
>> +++ b/tools/perf/tests/workloads/Build
>> @@ -26,3 +26,4 @@ CFLAGS_datasym.o = -g -O0 -fno-inline -U_FORTIFY_SOURCE
>> CFLAGS_traploop.o = -g -O0 -fno-inline -U_FORTIFY_SOURCE
>> CFLAGS_inlineloop.o = -g -O2
>> CFLAGS_deterministic.o = -g -O0 -fno-inline -U_FORTIFY_SOURCE
>> +CFLAGS_named_threads.o = -g -O0 -fno-inline -U_FORTIFY_SOURCE
>>
>> ---
>> base-commit: 7336514f41e75d44782fee7e0990d4195a3d3161
>> change-id: 20260611-james-cs-unformatted-per-thread-fix-followup-babf28a4e640
>>
>> Best regards,
>
prev parent reply other threads:[~2026-06-12 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 11:13 James Clark
2026-06-11 12:38 ` Leo Yan
2026-06-11 15:08 ` Arnaldo Carvalho de Melo
2026-06-11 15:11 ` James Clark
2026-06-11 18:54 ` David Laight
2026-06-12 8:24 ` James Clark [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453d71dc-1bd1-40e0-81e4-c578f64f438c@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=irogers@google.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®