From: Will Deacon <will.deacon@arm.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
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.zij@mx0.arm.com>
Subject: Re: [RFC 0/4] perf tool: Adding ratios support
Date: Thu, 17 Jan 2013 10:23:26 +0000 [thread overview]
Message-ID: <20130117102325.GA3699@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20130116133033.GC1042@krava.brq.redhat.com>
On Wed, Jan 16, 2013 at 01:30:33PM +0000, Jiri Olsa wrote:
> On Wed, Jan 16, 2013 at 01:13:18PM +0000, Will Deacon wrote:
> > On Tue, Jan 15, 2013 at 01:39:50PM +0000, Jiri Olsa wrote:
> > > The formula can currently contain any event from the set::events
> > > plus any number (int). There'll be support in future for outside
> > > values runtime and other if needed.
> >
> > Just to say that I *really* like this idea! If we extended it to include
> > other operators then it would help us on ARM, where we often have events
> > like 'cache accesses' and 'cache misses' but not 'cache hits'.
>
> great, thanks for sharing this
>
> The current operators set is just basic one to show the idea,
> it can/will be expanded.
Makes sense.
> > > My current thinking is to have generic formulas file(s) for architectural
> > > events and add arch-specific ones once when we have the support for
> > > non-architectural events (already sent RFC, v2 is on its way..).
> >
> > Would the architectural formula files also be in userspace, or is there any
> > merit to including useful PMU-specific formulae in sysfs, along with the
> > other PMU files?
>
> hum, isn't this too specific for sysfs files?
>
> I think that's going to be the perf tool specific info.. so it's going
> to be placed in its configuration files.
Understood. It would just be nice if the ARM perf backend could implement
more of the generic events, which would be possible if the kernel could
expose these formulae for those. Plumbing that together probably still
requires userspace changes though, in which case it's not worth it.
Will
next prev parent reply other threads:[~2013-01-17 10:28 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 [this message]
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
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=20130117102325.GA3699@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=a.p.zij@mx0.arm.com \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.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