All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	Julia Lawall <julia@diku.dk>, Tom Zanussi <tzanussi@gmail.com>,
	linux-kernel@vger.kernel.org,
	Matt Fleming <matt@console-pimps.org>
Subject: Re: [RFC PATCHv3] perf tools: add event grouping capability to "perf stat"
Date: Thu, 25 Nov 2010 09:00:09 +0100	[thread overview]
Message-ID: <1290672009.2072.558.camel@laptop> (raw)
In-Reply-To: <20101125074629.GC2538@nowhere>

On Thu, 2010-11-25 at 08:46 +0100, Frederic Weisbecker wrote:
> > perf record -e task-clock:freq=1000,cycles:period=0
> 
> Wouldn't this syntax clash with the flags we have on events already?
> 
> the u,k,p flags? 

>From stephane's email (to which you were CC'ed) http://lkml.org/lkml/2010/11/23/303

> $ perf record -e cycles:u:period=100000,instructions:k:freq=1500 -a -- sleep 5

The parser isn't particularly pretty, maybe its time to think about a parser generator?

  reply	other threads:[~2010-11-25  8:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25  1:54 [RFC PATCHv3] perf tools: add event grouping capability to "perf stat" Corey Ashford
2010-11-25  6:32 ` Peter Zijlstra
2010-11-25  7:46   ` Frederic Weisbecker
2010-11-25  8:00     ` Peter Zijlstra [this message]
2010-11-25  8:10       ` Frederic Weisbecker
2010-11-25  9:16     ` Stephane Eranian
2010-11-25 13:19   ` Stephane Eranian
2010-11-25 13:19   ` Stephane Eranian
2010-11-25 13:22     ` Stephane Eranian
2010-11-25 14:02     ` Peter Zijlstra
2010-11-25 14:07       ` Stephane Eranian
2010-11-25 14:12         ` Peter Zijlstra
2010-11-25 14:18           ` Stephane Eranian
2010-11-25 14:22             ` Peter Zijlstra
2010-11-25 15:10               ` Lin Ming
2010-11-25 15:15                 ` Peter Zijlstra
2010-11-25 15:19                   ` Lin Ming
2010-11-25 16:49             ` Arnaldo Carvalho de Melo
2010-11-26 19:22   ` Corey Ashford

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=1290672009.2072.558.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=julia@diku.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=tzanussi@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.