From: Jiri Olsa <jolsa@redhat.com>
To: Andreas Hollmann <hollmann@in.tum.de>
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: Tue, 2 Feb 2016 09:58:02 +0100 [thread overview]
Message-ID: <20160202085802.GA4257@krava.brq.redhat.com> (raw)
In-Reply-To: <CAGz0_-0k93OvSNgtnDMMTwYWxQuVnABqjfKC-KdmhGqv5H=C3A@mail.gmail.com>
On Tue, Feb 02, 2016 at 12:33:51AM +0100, Andreas Hollmann wrote:
> Thanks, this is what I was looking for!
>
> Why was the formula language abandoned? To restricted?
> It would be still useful for interval prints.
yea the python script interface is way more powerful
then whatever we would come with
>
> perf stat record und perf stat report work,
> but I get with perf script the following output/error. (Kernel 4.4,
> perf 4.5-rc2)
>
> $ perf script -s scripts/python/stat-cpi.py
> Display of symbols requested but neither sample IP nor sample address
> is selected. Hence, no addresses to convert to symbols.
hum, what was the record command? so I could recreate..
thanks,
jirka
next prev parent reply other threads:[~2016-02-02 8:58 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 [this message]
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
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=20160202085802.GA4257@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=hollmann@in.tum.de \
--cc=jolsa@kernel.org \
--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).