From: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
To: mpe@ellerman.id.au
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Madhavan Srinivasan <maddy@linux.vnet.ibm.com>
Subject: [PATCH v2 0/6] powerpc/perf: Export memory hierarchy level
Date: Mon, 6 Mar 2017 16:13:07 +0530 [thread overview]
Message-ID: <1488796993-25495-1-git-send-email-maddy@linux.vnet.ibm.com> (raw)
Power8/Power9 Perforence Monitoring Unit (PMU) supports
different sampling modes (SM) such as Random Instruction
Sampling (RIS), Random Load/Store Facility Sampling (RLS)
and Random Branch Sampling (RBS). Sample mode RLS updates
Sampled Instruction Event Register [SIER] bits with memory
hierarchy information for a cache reload. Patchset exports
the hierarchy information to the user via the perf_mem_data_src
object from SIER.
Patchset is a rebase of the work posted previously with minor
updates to it.
https://lkml.org/lkml/2015/6/11/92
Changelog v1:
- Fixed author-ship for the first patch and added suka's "Signed-off-by:".
Madhavan Srinivasan (5):
powerpc/perf: Export memory hierarchy info to user space
powerpc/perf: Support to export MMCRA[TEC*] field to userspace
powerpc/perf: Support to export SIERs bit in Power8
powerpc/perf: Support to export SIERs bit in Power9
powerpc/perf: Add Power8 mem_access event to sysfs
Sukadev Bhattiprolu (1):
powerpc/perf: Define big-endian version of perf_mem_data_src
arch/powerpc/include/asm/perf_event_server.h | 3 +
arch/powerpc/perf/core-book3s.c | 8 +++
arch/powerpc/perf/isa207-common.c | 86 ++++++++++++++++++++++++++++
arch/powerpc/perf/isa207-common.h | 26 ++++++++-
arch/powerpc/perf/power8-events-list.h | 6 ++
arch/powerpc/perf/power8-pmu.c | 4 ++
arch/powerpc/perf/power9-pmu.c | 2 +
include/uapi/linux/perf_event.h | 16 ++++++
tools/include/uapi/linux/perf_event.h | 16 ++++++
9 files changed, 166 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2017-03-06 10:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 10:43 Madhavan Srinivasan [this message]
2017-03-06 10:43 ` [PATCH v2 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src Madhavan Srinivasan
2017-03-06 11:22 ` Peter Zijlstra
2017-03-06 14:59 ` David Laight
2017-03-06 15:28 ` Peter Zijlstra
2017-03-07 9:58 ` Madhavan Srinivasan
2017-03-07 10:23 ` Peter Zijlstra
2017-03-13 11:15 ` Madhavan Srinivasan
2017-03-13 12:50 ` Peter Zijlstra
2017-03-14 9:01 ` Madhavan Srinivasan
2017-03-14 12:56 ` Peter Zijlstra
2017-03-15 6:20 ` Michael Ellerman
2017-03-15 12:23 ` Peter Zijlstra
2017-03-16 5:53 ` Madhavan Srinivasan
2017-03-16 5:47 ` Madhavan Srinivasan
2017-03-06 10:43 ` [PATCH v2 2/6] powerpc/perf: Export memory hierarchy info to user space Madhavan Srinivasan
2017-03-13 19:21 ` Sukadev Bhattiprolu
2017-03-06 10:43 ` [PATCH v2 3/6] powerpc/perf: Support to export MMCRA[TEC*] field to userspace Madhavan Srinivasan
2017-03-06 10:43 ` [PATCH v2 4/6] powerpc/perf: Support to export SIERs bit in Power8 Madhavan Srinivasan
2017-03-06 10:43 ` [PATCH v2 5/6] powerpc/perf: Support to export SIERs bit in Power9 Madhavan Srinivasan
2017-03-06 10:43 ` [PATCH v2 6/6] powerpc/perf: Add Power8 mem_access event to sysfs Madhavan Srinivasan
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=1488796993-25495-1-git-send-email-maddy@linux.vnet.ibm.com \
--to=maddy@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).