lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 Jan 2013 14:30:33 +0100
From:	Jiri Olsa <jolsa@...hat.com>
To:	Will Deacon <will.deacon@....com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zij@....arm.com>
Subject: Re: [RFC 0/4] perf tool: Adding ratios support

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:
> > hi,
> 
> Hi Jiri,
> 
> > adding support to predefine event ratios formulas so they could
> > be used easily in perf.
> > 
> > The formulas are handed in the config file with following format:
> > 
> >   set {
> >         events = {cycles,instructions,branch-instructions}:u
> > 
> >         cpi {
> >                 formula = cycles / instructions
> >                 desc = cycles per instruction
> >         }
> > 
> > 	branch-rate {
> >                 formula = branch-instructions / instructions
> >                 desc = branch rate
> >         }
> >   }
> > 
> >   The 'set' defines set of counter that share same events.
> >   Each 'set' defines:
> >     events   - event string that would go into stat/record -e option
> >     counters - any number of counters based on above events
> > 
> >   Each counter (cpi/branch-rate) defines
> >     formula - formula with that produce the counter number
> >               event names and numbers could be used
> >     desc    - text description of the counter
> > 
> > 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.

> 
> > 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.


jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ