From: Stephane Eranian <eranian@google.com>
To: linux-kernel@vger.kernel.org
Cc: acme@redhat.com, peterz@infradead.org, mingo@elte.hu,
ak@linux.intel.com, kan.liang@intel.com
Subject: [PATCH v2 0/2] perf/x86: fixes and improvement for Intel Atom PEBS support
Date: Thu, 3 Dec 2015 21:03:08 +0100 [thread overview]
Message-ID: <1449172990-30183-1-git-send-email-eranian@google.com> (raw)
This short series fixes total breakage of Intel Atom PEBS support in recent kernels.
The problems were introduced with the changes in the PEBS logic to handle
deeper buffer.
The first patch fixes PEBS and LBR problems, including NULL pointers, wrong pointer
arithmetic, and wrong pebs record layout assumption.
The second patch adds an alias for cycles:pp to Intel Atom given that perf record/top
uses cycles:pp nowadays.
In V2, we removed the alias function specific to Atom use use the one from Core2
because it is identical as suggested by Kan Liang.
Stephane Eranian (2):
perf/x86: fix PEBS and LBR issues on Intel Atom
perf/x86: enable cycles:pp for Intel Atom
arch/x86/kernel/cpu/perf_event_intel.c | 1 +
arch/x86/kernel/cpu/perf_event_intel_ds.c | 11 ++++++++++-
arch/x86/kernel/cpu/perf_event_intel_lbr.c | 11 +++++++----
3 files changed, 18 insertions(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2015-12-03 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 20:03 Stephane Eranian [this message]
2015-12-03 20:03 ` [PATCH v2 1/2] perf/x86: fix PEBS and LBR issues on Intel Atom Stephane Eranian
2015-12-03 20:51 ` Peter Zijlstra
2015-12-03 21:19 ` Andi Kleen
2015-12-03 20:03 ` [PATCH v2 2/2] perf/x86: enable cycles:pp for " Stephane Eranian
2015-12-03 20:14 ` Andi Kleen
2015-12-03 21:44 ` Stephane Eranian
2016-01-06 18:52 ` [tip:perf/core] perf/x86: Enable " tip-bot for Stephane Eranian
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=1449172990-30183-1-git-send-email-eranian@google.com \
--to=eranian@google.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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®