From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
eranian@google.com, namhyung@kernel.org, peterz@infradead.org,
mingo@kernel.org
Subject: Re: [PATCH 2/9] perf, tools, stat: Support up-scaling of events
Date: Tue, 11 Aug 2015 15:54:37 +0200 [thread overview]
Message-ID: <20150811135437.GB10703@krava.brq.redhat.com> (raw)
In-Reply-To: <20150811133805.GD4524@tassilo.jf.intel.com>
On Tue, Aug 11, 2015 at 06:38:05AM -0700, Andi Kleen wrote:
> On Tue, Aug 11, 2015 at 03:25:32PM +0200, Jiri Olsa wrote:
> > On Fri, Aug 07, 2015 at 06:06:18PM -0700, Andi Kleen wrote:
> > > From: Andi Kleen <ak@linux.intel.com>
> > >
> > > TopDown needs to multiply events by constants (for example
> > > the CPU Pipeline Width) to get the correct results.
> > > The kernel needs to export this factor.
> > >
> > > Today *.scale is only used to scale down metrics (divide), for example
> > > to scale bytes to MB.
> > >
> > > Repurpose negative scale to mean scaling up, that is multiplying.
> > > Implement the code for this in perf stat.
> > >
> > > Signed-off-by: Andi Kleen <ak@linux.intel.com>
> > > ---
> > > tools/perf/builtin-stat.c | 27 +++++++++++++++++++--------
> > > 1 file changed, 19 insertions(+), 8 deletions(-)
> > >
> > > diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> > > index ea5298a..2590c75 100644
> > > --- a/tools/perf/builtin-stat.c
> > > +++ b/tools/perf/builtin-stat.c
> > > @@ -179,6 +179,17 @@ static inline int nsec_counter(struct perf_evsel *evsel)
> > > return 0;
> > > }
> > >
> > > +static double scale_val(struct perf_evsel *counter, u64 val)
> > > +{
> > > + double uval = val;
> > > +
> > > + if (counter->scale < 0)
> > > + uval = val * (-counter->scale);
> > > + else if (counter->scale)
> > > + uval = val / counter->scale;
> >
> > hum, do you change the scale logic? the current scale > 0 works like:
> >
> > uval = val * counter->scale;
>
> Yes I define negative scales to mean "multiply by" See the description of the kernel
> patch for more details.
how about existing scale attributes, like in rapl code
jirka
next prev parent reply other threads:[~2015-08-11 13:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 1:06 Add top down metrics to perf stat Andi Kleen
2015-08-08 1:06 ` [PATCH 1/9] perf, tools: Dont stop PMU parsing on alias parse error Andi Kleen
2015-08-11 13:07 ` Jiri Olsa
2015-08-11 13:14 ` Andi Kleen
2015-08-11 13:24 ` Jiri Olsa
2015-08-11 13:40 ` Andi Kleen
2015-08-11 14:39 ` Jiri Olsa
2015-08-11 16:59 ` Andi Kleen
2015-08-08 1:06 ` [PATCH 2/9] perf, tools, stat: Support up-scaling of events Andi Kleen
2015-08-11 13:25 ` Jiri Olsa
2015-08-11 13:38 ` Andi Kleen
2015-08-11 13:54 ` Jiri Olsa [this message]
2015-08-11 17:00 ` Andi Kleen
2015-08-11 17:13 ` Jiri Olsa
2015-08-11 17:17 ` Andi Kleen
2015-08-08 1:06 ` [PATCH 3/9] perf, tools, stat: Basic support for TopDown in perf stat Andi Kleen
2015-08-08 1:06 ` [PATCH 4/9] perf, tools, stat: Add computation of TopDown formulas Andi Kleen
2015-08-08 1:06 ` [PATCH 5/9] x86, perf: Support sysfs files depending on SMT status Andi Kleen
2015-08-08 1:06 ` [PATCH 6/9] x86, perf: Add Top Down events to Intel Core Andi Kleen
2015-08-08 1:06 ` [PATCH 7/9] x86, perf: Add Top Down events to Intel Atom Andi Kleen
2015-08-08 1:06 ` [PATCH 8/9] perf, tools, stat: Add extra output of counter values with -v Andi Kleen
2015-08-08 1:06 ` [PATCH 9/9] perf, tools, stat: Force --per-core mode for .agg-per-core aliases Andi Kleen
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=20150811135437.GB10703@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®