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, adrian.hunter@intel.com,
x86@kernel.org, hpa@zytor.com, acme@infradead.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH 0/3] perf/x86/intel/pt: Add new packet enables
Date: Fri, 17 Jul 2015 16:34:07 +0300 [thread overview]
Message-ID: <1437140050-23363-1-git-send-email-alexander.shishkin@linux.intel.com> (raw)
Hi Peter,
There are new PT packets and handles to enable and configure them in the
new version if Intel Architecture SDM. This series deals with timing
related packets: adds bit definitions, cpuid enumeration and relevant
userspace-visible parts.
The bulk of work, as usual, is in the tooling, which I don't include in
this patchset, since it depends on Adrian's earlier work which is still
bouncing between him and the maintainers, but for the sake of completeness
I pushed it to my github tree [1] and Adrian is also sending it out for
review. So anybody interested in trying the whole thing out can pull it
from my tree.
This time around, however, there is no compile time dependency between
mine and his series, since all the relevant bits are communicated through
sysfs.
[1] https://github.com/virtuoso/linux-perf/commits/intel_pt
Alexander Shishkin (3):
perf/x86/intel/pt: Add new timing packet enables
perf/x86/intel/pt: Add an option to not force PSB+ on every
schedule-in
perf/x86/intel/bts: Set itrace_started in pmu::start to match the new
logic
arch/x86/include/asm/msr-index.h | 8 +++
arch/x86/kernel/cpu/intel_pt.h | 6 +++
arch/x86/kernel/cpu/perf_event.h | 1 +
arch/x86/kernel/cpu/perf_event_intel_bts.c | 1 +
arch/x86/kernel/cpu/perf_event_intel_pt.c | 78 ++++++++++++++++++++++++++++--
kernel/events/core.c | 2 -
6 files changed, 91 insertions(+), 5 deletions(-)
--
2.1.4
next reply other threads:[~2015-07-17 13:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 13:34 Alexander Shishkin [this message]
2015-07-17 13:34 ` [PATCH 1/3] perf/x86/intel/pt: Add new timing " Alexander Shishkin
2015-07-30 10:40 ` Peter Zijlstra
2015-07-30 11:57 ` Alexander Shishkin
2015-07-30 12:14 ` Peter Zijlstra
2015-07-30 13:15 ` [PATCH v1] " Alexander Shishkin
2015-08-04 8:55 ` [tip:perf/core] " tip-bot for Alexander Shishkin
2015-07-17 13:34 ` [PATCH 2/3] perf/x86/intel/pt: Add an option to not force PSB+ on every schedule-in Alexander Shishkin
2015-07-30 10:43 ` Peter Zijlstra
2015-07-30 11:53 ` Alexander Shishkin
2015-07-30 12:13 ` Peter Zijlstra
2015-07-30 12:49 ` Alexander Shishkin
2015-07-30 13:36 ` Alexander Shishkin
2015-07-30 13:48 ` [PATCH v1] perf/x86/intel/pt: Do not force sync packets " Alexander Shishkin
2015-07-30 15:24 ` Alexander Shishkin
2015-08-04 8:55 ` [tip:perf/core] " tip-bot for Alexander Shishkin
2015-07-31 11:47 ` [PATCH v2] " Alexander Shishkin
2015-07-17 13:34 ` [PATCH 3/3] perf/x86/intel/bts: Set itrace_started in pmu::start to match the new logic Alexander Shishkin
2015-09-08 12:02 ` Alexander Shishkin
2015-09-08 12:28 ` Peter Zijlstra
2015-09-13 10:56 ` [tip:perf/core] perf/x86/intel/bts: Set event-> hw.itrace_started " tip-bot for Alexander Shishkin
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=1437140050-23363-1-git-send-email-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@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
all inboxes | Powered by JetHome®