From: "Wangnan (F)" <wangnan0@huawei.com>
To: Brendan Gregg <brendan.d.gregg@gmail.com>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>
Subject: Re: perf bpf examples
Date: Thu, 7 Jul 2016 09:49:01 +0800 [thread overview]
Message-ID: <577DB50D.3040204@huawei.com> (raw)
In-Reply-To: <CAE40pdfDNi-+80az4YNa9asLGyOJc2e5RcPgFxz5FK9VwgRUtw@mail.gmail.com>
On 2016/7/7 4:29, Brendan Gregg wrote:
> G'Day,
>
> Are perf bpf examples shared anywhere? I've seen many posted to lkml
> (by Wang Nan), but don't see them in the linux source, or
> documentation. Would be very handy to throw them all up somewhere for
> searching/learning, if that hasn't already happened, eg, github.
>
> I was also looking to see if perf bpf supports sampling yet, but I
> don't think it does. Eg, imagine a:
>
> perf record -F 99 -e bpf_process_samples.c -a -- sleep 10
>
> which would require BPF attaching to perf_swevent_hrtimer()/etc, and
> also emitting a map (eg, sampled instruction pointer counts). I don't
> think perf currently does either, but was hoping for a collection of
> examples to double check.
Currently perf-bpf doesn't support dumpping resuling maps, but
we are working on it. I think you have read our uBPF approach:
http://article.gmane.org/gmane.linux.kernel/2203717
and
http://article.gmane.org/gmane.linux.kernel/2253579
in them we embeded a uBPF virtual machine to perf and give it
the ability to operate the result in maps.
Now we are trying another approach, introduce LLVM to perf,
compile data analysis and report to code. It would be much
powerful.
Thank you.
> Brendan
next prev parent reply other threads:[~2016-07-07 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 20:29 perf bpf examples Brendan Gregg
2016-07-07 1:49 ` Wangnan (F) [this message]
2016-07-07 17:54 ` Brendan Gregg
2016-07-07 17:58 ` Brendan Gregg
2016-07-08 4:18 ` Wangnan (F)
2016-07-08 7:57 ` Brendan Gregg
2016-07-08 10:46 ` Wangnan (F)
2016-07-08 16:35 ` Brendan Gregg
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=577DB50D.3040204@huawei.com \
--to=wangnan0@huawei.com \
--cc=brendan.d.gregg@gmail.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).