Re: [PATCH v2 3/3] perf metricgroup: Fix uncore metric expressions

2020-09-10 Thread Ian Rogers
On Wed, Sep 9, 2020 at 10:51 PM Namhyung Kim wrote: > > On Thu, Sep 10, 2020 at 12:26 PM Ian Rogers wrote: > > > > A metric like DRAM_BW_Use has on SkylakeX events uncore_imc/cas_count_read/ > > and uncore_imc/case_count_write/. These events open 6 events per socket > > with pmu names of uncore_i

Re: [PATCH v2 3/3] perf metricgroup: Fix uncore metric expressions

2020-09-09 Thread Namhyung Kim
On Thu, Sep 10, 2020 at 12:26 PM Ian Rogers wrote: > > A metric like DRAM_BW_Use has on SkylakeX events uncore_imc/cas_count_read/ > and uncore_imc/case_count_write/. These events open 6 events per socket > with pmu names of uncore_imc_[0-5]. The current metric setup code in > find_evsel_group ass

[PATCH v2 3/3] perf metricgroup: Fix uncore metric expressions

2020-09-09 Thread Ian Rogers
A metric like DRAM_BW_Use has on SkylakeX events uncore_imc/cas_count_read/ and uncore_imc/case_count_write/. These events open 6 events per socket with pmu names of uncore_imc_[0-5]. The current metric setup code in find_evsel_group assumes one ID will map to 1 event to be recorded in metric_event