linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Hollmann <hollmann@in.tum.de>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	"linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: User defined metrics for perf stat?
Date: Wed, 3 Feb 2016 12:43:48 +0100	[thread overview]
Message-ID: <CAGz0_-31qWb_0B2T_fpBwxGQkeg+PSATPS=uS5Ui1fKc8sVyiQ@mail.gmail.com> (raw)
In-Reply-To: <20160203074804.GA16045@krava.brq.redhat.com>

Thanks! Now it works.

Are there any other callbacks specific to the new functionality?

I saw this:

def stat__interval(time):
   ...

The name suggests that it is called once for each interval event entry?

Anything else?

Would it make sense to extend "perf script -g" to generate the callbacks?

2016-02-03 8:48 GMT+01:00 Jiri Olsa <jolsa@redhat.com>:
> On Tue, Feb 02, 2016 at 05:24:16PM +0100, Andreas Hollmann wrote:
>> Jiri, how do you handle raw counters with this python stat__*
>> callback? What is the name of the callback?
>
> you can use 'name' term like:
>   perf stat -e cycles,"cpu/config=0x6530160,name=krava/"
>
> and use following callback in your script:
>   def stat__krava(cpu, thread, time, val, ena, run):
>
>>
>> Is there any documentation on that? Thanks!
>
> no.. ;-)
>
> I'll try to come up with something.. meanwhile please just ask,
> I'd be happy to help you
>
> thanks,
> jirka

  reply	other threads:[~2016-02-03 11:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 16:53 User defined metrics for perf stat? Andreas Hollmann
2016-02-01 17:15 ` Arnaldo Carvalho de Melo
2016-02-01 17:27   ` Jiri Olsa
2016-02-01 23:33     ` Andreas Hollmann
2016-02-02  8:58       ` Jiri Olsa
2016-02-02  9:42         ` Andreas Hollmann
2016-02-02 16:24         ` Andreas Hollmann
2016-02-03  7:48           ` Jiri Olsa
2016-02-03 11:43             ` Andreas Hollmann [this message]
2016-02-03 14:09               ` Jiri Olsa
2016-02-03 15:25                 ` Andreas Hollmann
2016-02-05 14:12             ` Andreas Hollmann
2016-02-06 21:54               ` Jiri Olsa
2016-02-03 12:39         ` Milian Wolff
2016-02-03 14:11           ` Jiri Olsa
2016-02-03 14:18             ` eBPF counters for 'perf stat' e.g.: " Arnaldo Carvalho de Melo
2016-02-04  9:46               ` Wangnan (F)
2016-02-03 14:43             ` Milian Wolff

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='CAGz0_-31qWb_0B2T_fpBwxGQkeg+PSATPS=uS5Ui1fKc8sVyiQ@mail.gmail.com' \
    --to=hollmann@in.tum.de \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).