From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
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,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [RFC PATCH 0/6] perf: Add AUX data sampling
Date: Fri, 23 Sep 2016 14:27:20 +0300 [thread overview]
Message-ID: <20160923112726.5890-1-alexander.shishkin@linux.intel.com> (raw)
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.
The bulk of code is in 4/6, which adds attribute fields, creates
kernel events to generate the AUX data, takes samples and takes care
of all the tricky. 1/6 and 6/6 may also be considered separately from
this series. In particular, I suspect that 6/6 applies today to the
architectures that deliver PMIs as IRQs. Mathieu?
[1] https://git.kernel.org/cgit/linux/kernel/git/ash/linux.git/log/?h=perf-aux-sampling
Alexander Shishkin (6):
perf: Move mlock accounting to ring buffer allocation
perf: Add api to (de-)allocate AUX buffers for kernel counters
perf: Add a helper for looking up pmus by type
perf: Add infrastructure for using AUX data in perf samples
perf: Disable PMU around address filter adjustment
perf: Disable IRQs in address filter sync path
include/linux/perf_event.h | 12 ++
include/uapi/linux/perf_event.h | 16 +-
kernel/events/core.c | 419 +++++++++++++++++++++++++++++++++-------
kernel/events/internal.h | 24 ++-
kernel/events/ring_buffer.c | 210 ++++++++++++++++++--
5 files changed, 598 insertions(+), 83 deletions(-)
--
2.9.3
next reply other threads:[~2016-09-23 11:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 11:27 Alexander Shishkin [this message]
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 ` [RFC PATCH 0/6] perf: Add AUX data sampling Peter Zijlstra
2016-09-23 17:19 ` 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=20160923112726.5890-1-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=ak@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;
as well as URLs for NNTP newsgroup(s).