[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1290666760.2072.539.camel@laptop>
Date: Thu, 25 Nov 2010 07:32:40 +0100
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Corey Ashford <cjashfor@...ux.vnet.ibm.com>
Cc: Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Stephane Eranian <eranian@...gle.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Julia Lawall <julia@...u.dk>, Tom Zanussi <tzanussi@...il.com>,
linux-kernel@...r.kernel.org, Matt Fleming <matt@...sole-pimps.org>
Subject: Re: [RFC PATCHv3] perf tools: add event grouping capability to
"perf stat"
On Wed, 2010-11-24 at 17:54 -0800, Corey Ashford wrote:
> Add the ability to create multiple event groups, each with their own leader
> using the existing "-e <event>[,<event> ...] [-e <event>[,<event>]]"
> syntax. Each additional -e switch creates a new group, and each event
> listed within a -e switch is within that group.
>
> Changes since v1:
> - Because of a flub, v2 did not contain the changes I had intended to make,
> and instead, v2 had the same patch contents as v1.
> - When perf stat is not supplied any events on the command line, put
> each default event in its own group.
I like this, but could you also extend this to perf-record? its a bit
odd to diverge between the two.
Using Stephane's latest syntax changes you could actually do something
like:
perf record -e task-clock:freq=1000,cycles:period=0
Which would create a group with 1 sampling counter and a counting
counter (at which point we should probably start flipping
PERF_SAMPLE_READ).
Matt was working on supporting that (although not through cmdline
syntax) and teaching perf-report to cope with such output.
--
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