From: Peter Zijlstra <peterz@infradead.org>
To: Brendan Gregg <bgregg@netflix.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH v2 1/3] perf/core: Add a tracepoint for perf sampling
Date: Wed, 3 Aug 2016 11:48:05 +0200 [thread overview]
Message-ID: <20160803094805.GD6879@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1470192469-11910-2-git-send-email-bgregg@netflix.com>
On Wed, Aug 03, 2016 at 02:47:47AM +0000, Brendan Gregg wrote:
> When perf is performing hrtimer-based sampling, this tracepoint can be used
> by BPF to run additional logic on each sample. For example, BPF can fetch
> stack traces and frequency count them in kernel context, for an efficient
> profiler.
Urgh, no like.
And then next week we'll add a tracepoint to some other random pmu or
whatnot.
next prev parent reply other threads:[~2016-08-03 10:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 2:47 [PATCH v2 0/3] Add a tracepoint for BPF " Brendan Gregg
2016-08-03 2:47 ` [PATCH v2 1/3] perf/core: Add a tracepoint for " Brendan Gregg
2016-08-03 9:48 ` Peter Zijlstra [this message]
2016-08-03 18:57 ` Brendan Gregg
2016-08-04 14:28 ` Peter Zijlstra
2016-08-05 1:43 ` Alexei Starovoitov
2016-08-05 4:13 ` Brendan Gregg
2016-08-05 5:24 ` Alexei Starovoitov
2016-08-05 10:52 ` Peter Zijlstra
2016-08-05 17:22 ` Brendan Gregg
2016-08-08 9:57 ` Peter Zijlstra
2016-08-05 19:45 ` Alexei Starovoitov
2016-08-08 10:03 ` Peter Zijlstra
2016-08-03 2:47 ` [PATCH v2 2/3] samples/bpf: Add a sampling BPF example Brendan Gregg
2016-08-03 2:47 ` [PATCH v2 3/3] perf script: add bpf-output field to usage message Brendan Gregg
2016-08-09 19:16 ` [tip:perf/urgent] perf script: Add 'bpf-output' " tip-bot for 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=20160803094805.GD6879@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ast@kernel.org \
--cc=bgregg@netflix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=wangnan0@huawei.com \
/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
Powered by JetHome