All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
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: Tue, 15 Oct 2019 11:20:38 +0800	[thread overview]
Message-ID: <20191015032038.GA6336@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20191014141136.GD19627@kernel.org>

On Mon, Oct 14, 2019 at 11:11:36AM -0300, Arnaldo Carvalho de Melo wrote:
> 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.

Thanks a lot, Arnaldo.

  reply	other threads:[~2019-10-15  3:20 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
2019-10-15  3:20     ` Leo Yan [this message]
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=20191015032038.GA6336@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=jolsa@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.