From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/2] perf test: Avoid infinite loop for task exit case
Date: Mon, 14 Oct 2019 11:11:36 -0300 [thread overview]
Message-ID: <20191014141136.GD19627@kernel.org> (raw)
In-Reply-To: <20191011091942.29841-2-leo.yan@linaro.org>
Em Fri, Oct 11, 2019 at 05:19:42PM +0800, Leo Yan escreveu:
> When execute task exit testing case, Perf tool stucks in this case and
> doesn't return back on Arm64 Juno board.
>
> After dig into this issue, since Juno board has Arm's big.LITTLE CPUs,
> thus the PMUs are not compatible between the big CPUs and little CPUs.
> This leads to PMU event cannot be enabled properly when the traced task
> is migrated from one variant's CPU to another variant. Finally, the
> test case runs into infinite loop for cannot read out any event data
> after return from polling.
>
> Eventually, we need to work out formal solution to allow PMU events can
> be freely migrated from one CPU variant to another, but this is a
> difficult task and a different topic. This patch tries to fix the Perf
> test case to avoid infinite loop, when the testing detects 1000 times
> retrying for reading empty events, it will directly bail out and return
> failure. This allows the Perf tool can continue its other test cases.
Thanks, applied.
- Arnaldo
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
> tools/perf/tests/task-exit.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/tools/perf/tests/task-exit.c b/tools/perf/tests/task-exit.c
> index ca0a6ca43b13..d85c9f608564 100644
> --- a/tools/perf/tests/task-exit.c
> +++ b/tools/perf/tests/task-exit.c
> @@ -53,6 +53,7 @@ int test__task_exit(struct test *test __maybe_unused, int subtest __maybe_unused
> struct perf_cpu_map *cpus;
> struct perf_thread_map *threads;
> struct mmap *md;
> + int retry_count = 0;
>
> signal(SIGCHLD, sig_handler);
>
> @@ -132,6 +133,13 @@ int test__task_exit(struct test *test __maybe_unused, int subtest __maybe_unused
> out_init:
> if (!exited || !nr_exit) {
> evlist__poll(evlist, -1);
> +
> + if (retry_count++ > 1000) {
> + pr_debug("Failed after retrying 1000 times\n");
> + err = -1;
> + goto out_free_maps;
> + }
> +
> goto retry;
> }
>
> --
> 2.17.1
--
- Arnaldo
next prev parent reply other threads:[~2019-10-14 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 9:19 [PATCH v1 1/2] perf test: Report failure for mmap events Leo Yan
2019-10-11 9:19 ` [PATCH v1 2/2] perf test: Avoid infinite loop for task exit case Leo Yan
2019-10-11 14:38 ` Arnaldo Carvalho de Melo
2019-10-14 14:11 ` Arnaldo Carvalho de Melo [this message]
2019-10-15 3:20 ` Leo Yan
2019-10-21 23:19 ` [tip: perf/core] " tip-bot2 for Leo Yan
2019-10-14 14:09 ` [PATCH v1 1/2] perf test: Report failure for mmap events Arnaldo Carvalho de Melo
2019-10-21 23:19 ` [tip: perf/core] " tip-bot2 for Leo Yan
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=20191014141136.GD19627@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).