From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: Nick Forrington <nick.forrington@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf test: Remove atomics from test_loop to avoid test failures
Date: Tue, 21 Nov 2023 14:04:26 -0300 [thread overview]
Message-ID: <ZVzjGqKv9GxYATli@kernel.org> (raw)
In-Reply-To: <9e3355e0-f0d6-5f82-d2f6-b7e84bda996c@arm.com>
Em Fri, Nov 03, 2023 at 09:14:45AM +0000, James Clark escreveu:
> On 02/11/2023 16:22, Nick Forrington wrote:
> > The current use of atomics can lead to test failures, as tests (such as
> > tests/shell/record.sh) search for samples with "test_loop" as the
> > top-most stack frame, but find frames related to the atomic operation
> > (e.g. __aarch64_ldadd4_relax).
> > This change simply removes the "count" variable, as it is not necessary.
> > Fixes: 1962ab6f6e0b ("perf test workload thloop: Make count increments atomic")
> > Signed-off-by: Nick Forrington <nick.forrington@arm.com>
> > +++ b/tools/perf/tests/workloads/thloop.c
> > @@ -7,7 +7,6 @@
> > #include "../tests.h"
> > static volatile sig_atomic_t done;
> > -static volatile unsigned count;
> > /* We want to check this symbol in perf report */
> > noinline void test_loop(void);
> > @@ -19,8 +18,7 @@ static void sighandler(int sig __maybe_unused)
> > noinline void test_loop(void)
> > {
> > - while (!done)
> > - __atomic_fetch_add(&count, 1, __ATOMIC_RELAXED);
> > + while (!done);
> > }
> > static void *thfunc(void *arg)
> Reviewed-by: James Clark <james.clark@arm.com>
Thanks, applied to perf-tools-next.
- Arnaldo
next prev parent reply other threads:[~2023-11-21 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 16:22 [PATCH] perf test: Remove atomics from test_loop to avoid test failures Nick Forrington
2023-11-03 9:14 ` James Clark
2023-11-21 17:04 ` Arnaldo Carvalho de Melo [this message]
2023-11-24 19:57 ` Michael Petlan
2023-11-25 3:05 ` Leo Yan
2023-11-25 19:10 ` Nick Forrington
2023-11-26 7:41 ` Leo Yan
2023-11-27 13:20 ` Arnaldo Carvalho de Melo
2023-11-27 13:29 ` Leo Yan
2023-11-27 10:45 ` James Clark
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=ZVzjGqKv9GxYATli@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=nick.forrington@arm.com \
/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