From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: James Clark <james.clark@arm.com>
Cc: Leo Yan <leo.yan@linaro.org>,
coresight@lists.linaro.org, suzuki.poulose@arm.com,
linux-perf-users@vger.kernel.org, mathieu.poirier@linaro.org,
mike.leach@linaro.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf test: Fix test_arm_coresight.sh failures on Juno
Date: Fri, 14 Oct 2022 10:33:47 -0300 [thread overview]
Message-ID: <Y0llO2itucU5wwxR@kernel.org> (raw)
In-Reply-To: <7dcf8bc5-4182-cf73-59ec-86e113ab2c17@arm.com>
Em Mon, Oct 10, 2022 at 10:21:22AM +0100, James Clark escreveu:
> On 10/10/2022 08:41, Leo Yan wrote:
> > On Thu, Oct 06, 2022 at 04:11:05PM +0100, James Clark wrote:
> >> Error:
> >> The perf.data data has no samples!
> >> 0
> > Thanks for confirmation. It's a bit weird that your Juno board doesn't
> > produce all zeros for timestamp packets.
> >> I think the issue is that ls is quite quick to run, so not much trace is
> >> generated for Perf. And it just depends on the scheduling which is
> >> slightly different on Juno. I don't think it's a bug. On N1SDP there are
> >> only 134 samples generated with i1000i, so it could probably end up with
> >> a random run generating 0 there too.
> > Agreed, changing to smaller interval makes sense for me.
> > Reviewed-by: Leo Yan <leo.yan@linaro.org>
> Thanks for the review Leo
Thanks, applied.
- Arnaldo
next prev parent reply other threads:[~2022-10-14 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 14:05 [PATCH] perf test: Fix test_arm_coresight.sh failures on Juno James Clark
2022-10-06 14:48 ` Leo Yan
2022-10-06 15:11 ` James Clark
2022-10-10 7:41 ` Leo Yan
2022-10-10 9:21 ` James Clark
2022-10-14 13:33 ` Arnaldo Carvalho de Melo [this message]
2022-10-13 13:45 ` arm coresight txt triggers build warning: (was [PATCH] perf test: Fix test_arm_coresight.sh failures on Juno) Christian Borntraeger
2022-10-13 14:54 ` 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=Y0llO2itucU5wwxR@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@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 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.