From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V1] perf: qcom: Add L3 cache PMU driver
Date: Mon, 21 Mar 2016 10:54:07 +0000 [thread overview]
Message-ID: <20160321105407.GD23397@arm.com> (raw)
In-Reply-To: <20160321103507.GB17326@leverpostej>
On Mon, Mar 21, 2016 at 10:35:08AM +0000, Mark Rutland wrote:
> On Fri, Mar 18, 2016 at 04:37:02PM -0400, Agustin Vega-Frias wrote:
> > This adds a new dynamic PMU to the Perf Events framework to program
> > and control the L3 cache PMUs in some Qualcomm Technologies SOCs.
> >
> > The driver supports a distributed cache architecture where the overall
> > cache is comprised of multiple slices each with its own PMU. The driver
> > aggregates counts across the whole system to provide a global picture
> > of the metrics selected by the user.
> >
> > The driver exports formatting and event information to sysfs so it can
> > be used by the perf user space tools with the syntaxes:
> > perf stat -a -e l3cache/read-miss/
> > perf stat -a -e l3cache/event=0x21/
> >
> > Signed-off-by: Agustin Vega-Frias <agustinv@codeaurora.org>
> > ---
> > arch/arm64/kernel/Makefile | 4 +
> > arch/arm64/kernel/perf_event_qcom_l3_cache.c | 816 +++++++++++++++++++++++++++
> > 2 files changed, 820 insertions(+)
> > create mode 100644 arch/arm64/kernel/perf_event_qcom_l3_cache.c
>
> Move this to drivers/bus (where the CCI and CCN PMU drivers live), or
> drivers/perf (where some common infrastructure lives).
Please stick to drivers/perf, as I have a vague plan to move the CCI/CCN
PMU code out of drivers/bus and into drivers/perf (which didn't exist
when they were originally upstreamed).
Will
next prev parent reply other threads:[~2016-03-21 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 20:37 [PATCH V1] perf: qcom: Add L3 cache PMU driver Agustin Vega-Frias
2016-03-21 9:04 ` Peter Zijlstra
2016-03-21 15:56 ` agustinv at codeaurora.org
2016-03-21 16:00 ` Peter Zijlstra
2016-03-21 10:35 ` Mark Rutland
2016-03-21 10:54 ` Will Deacon [this message]
2016-03-21 12:04 ` Peter Zijlstra
2016-03-21 16:37 ` agustinv at codeaurora.org
2016-03-21 16:06 ` agustinv at codeaurora.org
2016-03-22 18:33 ` agustinv at codeaurora.org
[not found] ` <56F26FF1.90002@arm.com>
2016-03-23 12:36 ` agustinv at codeaurora.org
2016-03-23 14:46 ` Peter Zijlstra
2016-03-22 20:48 ` Peter Zijlstra
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=20160321105407.GD23397@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.