From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andreas Hollmann <hollmann@in.tum.de>,
Jiri Olsa <jolsa@kernel.org>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: User defined metrics for perf stat?
Date: Mon, 1 Feb 2016 18:27:55 +0100 [thread overview]
Message-ID: <20160201172755.GA27366@krava.redhat.com> (raw)
In-Reply-To: <20160201171540.GB20817@kernel.org>
On Mon, Feb 01, 2016 at 02:15:40PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Sun, Jan 31, 2016 at 05:53:49PM +0100, Andreas Hollmann escreveu:
> > Hi,
> >
> > is there any way to create user defined metrics in perf stat?
> >
> > Many hardware performance counters make only sense if you relate them
> > to other counters, so it would be nice to have it in perf.
>
> I think what you want is the 'perf stat recording' feature that was
> recently merged, contributed by Jiri Olsa, that I am CCing this reply.
> Jiri, is there something still to be merged in that series?
heya,
nope.. everything is in ;-)
Andreas,
please check on the series changelog:
http://marc.info/?l=linux-kernel&m=145207742329050&w=2
it describes the scripting usage together with
stat recording/reporting
let me know if you have other questions,
thanks,
jirka
next prev parent reply other threads:[~2016-02-01 17:27 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 [this message]
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
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=20160201172755.GA27366@krava.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).