From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ulrich Drepper <drepper@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andi Kleen <andi@firstfloor.org>, David Ahern <dsahern@gmail.com>
Subject: Re: [RFC 0/4] perf tool: Adding ratios support
Date: Thu, 17 Jan 2013 17:05:16 +0100 [thread overview]
Message-ID: <20130117160516.GA4724@krava.brq.redhat.com> (raw)
In-Reply-To: <87pq14lixn.fsf@sejong.aot.lge.com>
On Thu, Jan 17, 2013 at 10:03:32AM +0900, Namhyung Kim wrote:
> Hi,
>
> On Wed, 16 Jan 2013 10:12:14 -0500, Ulrich Drepper wrote:
> > On Wed, Jan 16, 2013 at 9:25 AM, Jiri Olsa <jolsa@redhat.com> wrote:
> >> I was thinking having config files (global and arch specific)
> >> comming with perf having predefined formulas.
> >
> > All the more reason to not mention the file name or really any source
> > for the definition of the formula in the name,
> >
> >
> >> 1) -e 'ratio/branch-rate/' # special event class
> >> 2) -e 'ratio-branch-rate' # 'ratio-' prefix
> >> 3) -e cpu/branch-rate/ # handled like aliases, ratio name would need to be unique
> >> ... ?
> >
> > I think 3 is the most extensible. Perhaps use the syntax used in
> > other places. We have these :u suffixes etc. Perhaps have :r or :R
> > or whatever.
>
> I don't think it's a good idea. The ':r' syntax is for modifiers to the
> existing events so it doesn't match to this case IMHO.
>
> I prefer a special event class like 1 since it's possible to include
> non-cpu events to a ratio/formular. In that case, using 'cpu' in the
> PMU name can be misleading.
>
> >
> > Given the other comments, we might want to avoid right away "ratio".
> > If the mechanism is generalized it could be used to express "counter1
> > - counter2" for events which cannot be expressed with a single counter
> > but are not really ratios.
>
> Agreed. Looks like "formular" is better.
agreed, I think I wouldn't touch modifiers for this
also, 'ratio' is not good choice, formula seems better
jirka
prev parent reply other threads:[~2013-01-17 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 13:39 Jiri Olsa
2013-01-15 13:39 ` [PATCH 1/4] perf tool: Remove unused 'unset' parameter from parse_events Jiri Olsa
2013-01-25 11:52 ` [tip:perf/core] perf tools: " tip-bot for Jiri Olsa
2013-01-15 13:39 ` [PATCH 2/4] perf tool: Add formula interface to interface ratio definitions Jiri Olsa
2013-01-15 13:39 ` [PATCH 3/4] perf stat: Adding -f option to load and process ratios Jiri Olsa
2013-01-15 13:39 ` [PATCH 4/4] perf tool: Adding formula.conf file for testing Jiri Olsa
2013-01-16 13:13 ` [RFC 0/4] perf tool: Adding ratios support Will Deacon
2013-01-16 13:30 ` Jiri Olsa
2013-01-17 10:23 ` Will Deacon
2013-01-21 19:13 ` Jiri Olsa
2013-01-22 9:45 ` Will Deacon
2013-01-16 14:00 ` Ulrich Drepper
2013-01-16 14:25 ` Jiri Olsa
2013-01-16 15:12 ` Ulrich Drepper
2013-01-17 1:03 ` Namhyung Kim
2013-01-17 16:05 ` Jiri Olsa [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=20130117160516.GA4724@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=drepper@gmail.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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
Powered by JetHome