[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y0llO2itucU5wwxR@kernel.org>
Date: Fri, 14 Oct 2022 10:33:47 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: James Clark <james.clark@....com>
Cc: Leo Yan <leo.yan@...aro.org>, coresight@...ts.linaro.org,
suzuki.poulose@....com, linux-perf-users@...r.kernel.org,
mathieu.poirier@...aro.org, mike.leach@...aro.org,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf test: Fix test_arm_coresight.sh failures on Juno
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@...aro.org>
> Thanks for the review Leo
Thanks, applied.
- Arnaldo
Powered by blists - more mailing lists