linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>,
	Haiyan Song <haiyanx.song@intel.com>,
	Jin Yao <yao.jin@linux.intel.com>,
	Song Liu <songliubraving@fb.com>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	John Garry <john.garry@huawei.com>, Leo Yan <leo.yan@linaro.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Paul Clarke <pc@us.ibm.com>, LKML <linux-kernel@vger.kernel.org>,
	kajoljain <kjain@linux.ibm.com>,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	Stephane
Subject: Re: [PATCH v4 12/12] perf test: improve pmu event metric testing
Date: Sun, 3 May 2020 19:06:08 +0200	[thread overview]
Message-ID: <20200503170608.GA1915271@krava> (raw)
In-Reply-To: <CAP-5=fXrwcz+MMF0Dqd_UnoXoTo1iO7T3-ENX0fzytPmJWmtoA@mail.gmail.com>

On Sun, May 03, 2020 at 08:26:22AM -0700, Ian Rogers wrote:
> On Sun, May 3, 2020 at 7:56 AM Jiri Olsa <jolsa@redhat.com> wrote:
> >
> > On Fri, May 01, 2020 at 10:33:33AM -0700, Ian Rogers wrote:
> > > Add a basic floating point number test to expr.
> > > Break pmu-events test into 2 and add a test to verify that all pmu metric
> > > expressions simply parse. Try to parse all metric ids/events, failing if
> > > metrics for the current architecture fail to parse.
> > >
> > > Tested on skylakex with the patch set in place. May fail on other
> > > architectures if metrics are invalid.
> >
> > yep, failing for me (-vvv output below).. could you plz
> > detect that and skip the test ?
> 
> Thanks, filtering the verbose output we have just 1 parse event failure:
> 
> Parse event failed: id 'arb/event=0x80,umask=0x2,thresh=1/' metric
> 'DRAM_Parallel_Reads' expr 'arb@event\=0x80\,umask\=0x2@ /
> arb@event\=0x80\,umask\=0x2\,thresh\=1@'
> Error string 'unknown term 'thresh' for pmu 'uncore_arb'' help 'valid
> terms: event,edge,inv,umask,cmask,config,config1,config2,name,period,freq,branch_type,time,call-graph,stack-size,no-inherit,inherit,max-stack,nr,no-overwrite,overwrite,driver-config,percore,aux-output,aux-sample-size'
> 
> This looks like a bug in skl-metrics.json:
> 
>    {
>         "BriefDescription": "Average number of parallel data read
> requests to external memory. Accounts for demand loads and L1/L2
> prefetches",
>         "MetricExpr": "arb@event\\=0x80\\,umask\\=0x2@ /
> arb@event\\=0x80\\,umask\\=0x2\\,thresh\\=1@",
>         "MetricGroup": "Memory_BW",
>         "MetricName": "DRAM_Parallel_Reads"
>     },
> 
> which can be fixed by removing "\\,thresh\\=1" but looking at the
> expression this will just make the expression yield a value of 1. As
> this is an Intel json file could they comment? Jiri, could you be
> missing a patch on the kernel side? We could lower this failure to
> just a diagnostic message to land this set of patches, let me know
> what you'd like me to do.

I applied this on current Arnaldo's perf/core.. not sure there's
more pending changes out there

I'd like not to delay this patchset too long.. could we push the
first 10 patches and solve the rest in separate change?

thanks,
jirka

  parent reply	other threads:[~2020-05-03 17:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 17:33 [PATCH v4 00/12] perf metric fixes and test Ian Rogers
2020-05-01 17:33 ` [PATCH v4 01/12] perf expr: unlimited escaped characters in a symbol Ian Rogers
2020-05-04  6:48   ` kajoljain
2020-05-01 17:33 ` [PATCH v4 02/12] perf metrics: fix parse errors in cascade lake metrics Ian Rogers
2020-05-01 17:33 ` [PATCH v4 03/12] perf metrics: fix parse errors in skylake metrics Ian Rogers
2020-05-01 17:33 ` [PATCH v4 04/12] perf expr: allow ',' to be an other token Ian Rogers
2020-05-01 17:33 ` [PATCH v4 05/12] perf expr: increase max other Ian Rogers
2020-05-01 17:33 ` [PATCH v4 06/12] perf expr: parse numbers as doubles Ian Rogers
2020-05-04  6:50   ` kajoljain
2020-05-01 17:33 ` [PATCH v4 07/12] perf expr: debug lex if debugging yacc Ian Rogers
2020-05-01 17:33 ` [PATCH v4 08/12] perf metrics: fix parse errors in power8 metrics Ian Rogers
2020-05-01 17:33 ` [PATCH v4 09/12] perf metrics: fix parse errors in power9 metrics Ian Rogers
2020-05-01 17:33 ` [PATCH v4 10/12] perf expr: print a debug message for division by zero Ian Rogers
2020-05-01 17:33 ` [PATCH v4 11/12] perf parse-events: expand add PMU error/verbose messages Ian Rogers
2020-05-01 17:33 ` [PATCH v4 12/12] perf test: improve pmu event metric testing Ian Rogers
     [not found]   ` <20200503145553.GA1865281@krava>
     [not found]     ` <CAP-5=fXrwcz+MMF0Dqd_UnoXoTo1iO7T3-ENX0fzytPmJWmtoA@mail.gmail.com>
2020-05-03 17:06       ` Jiri Olsa [this message]
2020-05-03 17:31         ` Ian Rogers
2020-05-03 22:16           ` Jiri Olsa
2020-05-07  8:44 ` [PATCH v4 00/12] perf metric fixes and test Jiri Olsa
2020-05-07 16:00   ` Arnaldo Carvalho de Melo
2020-05-11 15:32   ` Arnaldo Carvalho de Melo
2020-05-11 16:12     ` Ian Rogers
2020-05-13  6:32       ` Ian Rogers

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=20200503170608.GA1915271@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=haiyanx.song@intel.com \
    --cc=irogers@google.com \
    --cc=john.garry@huawei.com \
    --cc=kan.liang@linux.intel.com \
    --cc=kjain@linux.ibm.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pc@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=songliubraving@fb.com \
    --cc=yao.jin@linux.intel.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;
as well as URLs for NNTP newsgroup(s).