linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Kajol Jain <kjain@linux.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Paul Clarke <pc@us.ibm.com>, Jiri Olsa <jolsa@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	Jin Yao <yao.jin@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users <linux-perf-users@vger.kernel.org>,
	maddy@linux.ibm.com, Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Anju T Sudhakar <anju@linux.vnet.ibm.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	nasastry@in.ibm.com
Subject: Re: [PATCH] perf/tools/pmu-events/powerpc: Added nest imc metric events
Date: Mon, 6 Jul 2020 09:38:55 -0300	[thread overview]
Message-ID: <20200706123855.GI1320@kernel.org> (raw)
In-Reply-To: <CAP-5=fUraGwGLC79g51eZpcB9e2P=tOmz7U7G=RAu+Hmjjjxzw@mail.gmail.com>

Em Sun, Jul 05, 2020 at 06:30:30PM -0700, Ian Rogers escreveu:
> On Thu, Jul 2, 2020 at 11:57 PM Kajol Jain <kjain@linux.ibm.com> wrote:
> >
> > Added nest imc metric events.
> 
> Acked-by: Ian Rogers <irogers@google.com>

Thanks, applied.

- Arnaldo
 
> > Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
> > ---
> >  .../arch/powerpc/power9/nest_metrics.json     | 35 +++++++++++++++++++
> >  1 file changed, 35 insertions(+)
> >
> > diff --git a/tools/perf/pmu-events/arch/powerpc/power9/nest_metrics.json b/tools/perf/pmu-events/arch/powerpc/power9/nest_metrics.json
> > index c121e526442a..8383a37647ad 100644
> > --- a/tools/perf/pmu-events/arch/powerpc/power9/nest_metrics.json
> > +++ b/tools/perf/pmu-events/arch/powerpc/power9/nest_metrics.json
> > @@ -15,5 +15,40 @@
> >         "MetricExpr": "(hv_24x7@PM_PB_CYC\\,chip\\=?@ )",
> >          "MetricName": "PowerBUS_Frequency",
> >          "ScaleUnit": "2.5e-7GHz"
> > +    },
> > +    {
> > +       "MetricExpr" : "nest_mcs01_imc@PM_MCS01_128B_RD_DISP_PORT01@ + nest_mcs01_imc@PM_MCS01_128B_RD_DISP_PORT23@",
> > +       "MetricName" : "mcs01-read",
> > +       "MetricGroup" : "memory_bw",
> > +       "ScaleUnit": "6.1e-5MB"
> 
> nit: I'm guessing this is from:
> 64.0/(1024.0*1024.0) = 6.103515625e-05
> and for reference:
> 64.0/(1000.0*1000.0) = 6.3999999999999997e-05
> should the unit be MiB?
> https://en.wikipedia.org/wiki/Kibibyte
> 
> Searching around I only see knightslanding using MiB but it seems to
> be using it in the 1000^2 case which probably means it should be MB:
> knightslanding/uncore-memory.json:        "ScaleUnit": "6.4e-05MiB"
> 
> Given there is some confusion I wonder if it makes sense to just make
> this 0.015625B and then we have a utility function that selects the
> best unit for "bytes" with config options similar to --big-num?
> 
> Thanks,
> Ian
> 
> > +    },
> > +    {
> > +       "MetricExpr" : "nest_mcs23_imc@PM_MCS23_128B_RD_DISP_PORT01@ + nest_mcs23_imc@PM_MCS23_128B_RD_DISP_PORT23@",
> > +       "MetricName" : "mcs23-read",
> > +       "MetricGroup" : "memory_bw",
> > +       "ScaleUnit": "6.1e-5MB"
> > +    },
> > +    {
> > +       "MetricExpr" : "nest_mcs01_imc@PM_MCS01_128B_WR_DISP_PORT01@ + nest_mcs01_imc@PM_MCS01_128B_WR_DISP_PORT23@",
> > +       "MetricName" : "mcs01-write",
> > +       "MetricGroup" : "memory_bw",
> > +       "ScaleUnit": "6.1e-5MB"
> > +    },
> > +    {
> > +       "MetricExpr" : "nest_mcs23_imc@PM_MCS23_128B_WR_DISP_PORT01@ + nest_mcs23_imc@PM_MCS23_128B_WR_DISP_PORT23@",
> > +       "MetricName" : "mcs23-write",
> > +       "MetricGroup" : "memory-bandwidth",
> > +       "ScaleUnit": "6.1e-5MB"
> > +    },
> > +    {
> > +       "MetricExpr" : "nest_powerbus0_imc@PM_PB_CYC@",
> > +       "MetricName" : "powerbus_freq",
> > +       "ScaleUnit": "1e-9GHz"
> > +    },
> > +    {
> > +       "MetricExpr" : "(nest_mcs01_imc@PM_MCS01_128B_RD_DISP_PORT01@ + nest_mcs01_imc@PM_MCS01_128B_RD_DISP_PORT23@ + nest_mcs23_imc@PM_MCS23_128B_RD_DISP_PORT01@ + nest_mcs23_imc@PM_MCS23_128B_RD_DISP_PORT23@ + nest_mcs01_imc@PM_MCS01_128B_WR_DISP_PORT01@ + nest_mcs01_imc@PM_MCS01_128B_WR_DISP_PORT23@ + nest_mcs23_imc@PM_MCS23_128B_WR_DISP_PORT01@ + nest_mcs23_imc@PM_MCS23_128B_WR_DISP_PORT23@)",
> > +       "MetricName" : "Memory-bandwidth-MCS",
> > +       "MetricGroup" : "memory_bw",
> > +       "ScaleUnit": "6.1e-5MB"
> >      }
> >  ]
> > --
> > 2.17.1
> >

-- 

- Arnaldo

      reply	other threads:[~2020-07-06 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03  6:56 [PATCH] perf/tools/pmu-events/powerpc: Added nest imc metric events Kajol Jain
2020-07-06  1:30 ` Ian Rogers
2020-07-06 12:38   ` Arnaldo Carvalho de Melo [this message]

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=20200706123855.GI1320@kernel.org \
    --to=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anju@linux.vnet.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@linux.intel.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=nasastry@in.ibm.com \
    --cc=pc@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.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).