From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, vince@deater.net,
eranian@google.com, Arnaldo Carvalho de Melo <acme@infradead.org>,
tglx@linutronix.de, ak@linux.intel.com
Subject: Re: [RFC PATCH 0/6] perf: Add AUX data sampling
Date: Fri, 23 Sep 2016 13:49:17 +0200 [thread overview]
Message-ID: <20160923114917.GI5008@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160923112726.5890-1-alexander.shishkin@linux.intel.com>
On Fri, Sep 23, 2016 at 02:27:20PM +0300, Alexander Shishkin wrote:
> Hi Peter,
>
> This is an RFC, I'm not sending the tooling bits in this series,
> although they can be found here [1].
>
> This series introduces AUX data sampling for perf events, which in
> case of our instruction/branch tracing PMUs like Intel PT, BTS, CS
> ETM means execution flow history leading up to a perf event's
> overflow.
This fails to explain _WHY_ this is a good thing to have. What kind of
analysis does this enable, and is that fully implemented in [1] (I
didn't look).
Please provide a bit more justification.
next prev parent reply other threads:[~2016-09-23 11:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 11:27 Alexander Shishkin
2016-09-23 11:27 ` [RFC PATCH 1/6] perf: Move mlock accounting to ring buffer allocation Alexander Shishkin
2016-09-23 12:14 ` Peter Zijlstra
2016-09-23 14:27 ` Alexander Shishkin
2016-09-23 15:27 ` Peter Zijlstra
2016-09-23 15:58 ` Alexander Shishkin
2016-09-23 17:26 ` Andi Kleen
2016-09-23 20:28 ` Peter Zijlstra
2016-09-26 8:27 ` Alexander Shishkin
2016-09-26 9:03 ` Peter Zijlstra
2016-09-26 12:39 ` Alexander Shishkin
2016-09-26 16:13 ` Alexander Shishkin
2016-09-23 11:27 ` [RFC PATCH 2/6] perf: Add api to (de-)allocate AUX buffers for kernel counters Alexander Shishkin
2016-09-23 11:27 ` [RFC PATCH 3/6] perf: Add a helper for looking up pmus by type Alexander Shishkin
2016-09-23 11:27 ` [RFC PATCH 4/6] perf: Add infrastructure for using AUX data in perf samples Alexander Shishkin
2016-09-23 11:27 ` [RFC PATCH 5/6] perf: Disable PMU around address filter adjustment Alexander Shishkin
2016-09-23 11:27 ` [RFC PATCH 6/6] perf: Disable IRQs in address filter sync path Alexander Shishkin
2016-09-26 16:18 ` Alexander Shishkin
2016-10-04 16:49 ` Mathieu Poirier
2016-09-23 11:49 ` Peter Zijlstra [this message]
2016-09-23 17:19 ` [RFC PATCH 0/6] perf: Add AUX data sampling Andi Kleen
2016-09-23 20:35 ` Peter Zijlstra
2016-09-23 22:34 ` Andi Kleen
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=20160923114917.GI5008@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vince@deater.net \
/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