From: Milian Wolff <milian.wolff@kdab.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andreas Hollmann <hollmann@in.tum.de>,
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, 03 Feb 2016 13:39:20 +0100 [thread overview]
Message-ID: <17343448.BlG9640ky3@milian-kdab2> (raw)
In-Reply-To: <20160202085802.GA4257@krava.brq.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Tuesday, February 2, 2016 9:58:02 AM CET Jiri Olsa wrote:
> 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
How does this compare to the ongoing eBPF effort? Will we be able to do eBPF
based in-kernel aggregation for perf stat in the future?
Thanks
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2016-02-03 12:39 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
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 [this message]
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=17343448.BlG9640ky3@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=hollmann@in.tum.de \
--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).