From: Ashok Kumar <ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
will.deacon-5wv7dgnIgG8@public.gmane.org,
Suzuki.Poulose-5wv7dgnIgG8@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
catalin.marinas-5wv7dgnIgG8@public.gmane.org
Cc: jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org,
jglauber-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org,
Ashok Kumar <ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Subject: [PATCH v5 0/7] arm64: perf: Broadcom Vulcan PMU support
Date: Tue, 19 Apr 2016 11:54:15 -0700 [thread overview]
Message-ID: <1461092062-7484-1-git-send-email-ashoks@broadcom.com> (raw)
Cleaned up event naming convention as per ARM ARM.
Added macros for complete ARMv8 recommended implementation defined events.
changed pmu register access to make use of read/write_sys_reg.
Common architectural and micro-architectural events which are exported to /sys
are now filtered using PMCEIDn_EL0
Added support for Broadcom Vulcan PMU.
changes since v4 [4]:
* Used read/write_sys_reg for pmu register access as per Suzuki's review
comment from v2.
changes since v3 [3]:
* Changed the order of patchset to match devicetree submission guidelines.
* Rebased on 4.6-rc3
changes since v2 [2]:
* Changed event filtering mechanism to use is_visible function pointer
of attribute_group instead of copying to a new events attribute
structure as per Mark's review comments.
changes since v1 [1]:
Incorporated the following review comments from Will.
* cleaned up event naming convention as per ARM ARM
* Filtered common events based on PMCEIDn_EL0
* Removed exposing implementation defined events to /sys.
[1] http://www.spinics.net/lists/arm-kernel/msg490954.html
[2] http://www.spinics.net/lists/arm-kernel/msg492439.html
[3] http://www.spinics.net/lists/arm-kernel/msg492941.html
[4] http://www.spinics.net/lists/arm-kernel/msg496151.html
Ashok Kumar (7):
Documentation: arm64: pmu: Add Broadcom Vulcan PMU binding
arm64: dts: Add Broadcom Vulcan PMU in dts
arm64/perf: Changed events naming as per ARM ARM
arm64/perf: Define complete ARMv8 recommended implementation defined
events
arm64/perf: Access pmu register using <read/write>_sys_reg
arm64/perf: Filter common events based on PMCEIDn_EL0
arm64/perf: Add Broadcom Vulcan PMU support
Documentation/devicetree/bindings/arm/pmu.txt | 3 +-
arch/arm64/boot/dts/broadcom/vulcan.dtsi | 2 +-
arch/arm64/kernel/perf_event.c | 550 +++++++++++++++++---------
include/linux/perf/arm_pmu.h | 2 +
4 files changed, 373 insertions(+), 184 deletions(-)
--
2.1.0
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-04-19 18:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 18:54 Ashok Kumar [this message]
[not found] ` <1461092062-7484-1-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-19 18:54 ` [PATCH v5 1/7] Documentation: arm64: pmu: Add Broadcom Vulcan PMU binding Ashok Kumar
[not found] ` <1461092062-7484-2-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-20 11:15 ` Mark Rutland
2016-04-19 18:54 ` [PATCH v5 2/7] arm64: dts: Add Broadcom Vulcan PMU in dts Ashok Kumar
[not found] ` <1461092062-7484-3-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-20 11:16 ` Mark Rutland
2016-04-19 18:54 ` [PATCH v5 3/7] arm64/perf: Changed events naming as per ARM ARM Ashok Kumar
[not found] ` <1461092062-7484-4-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-20 13:34 ` Mark Rutland
2016-04-20 13:43 ` Mark Rutland
2016-04-21 9:21 ` Ashok Kumar
2016-04-21 9:21 ` Ashok Kumar
2016-04-21 9:21 ` Ashok Kumar
[not found] ` <20160421092107.GA3673@ashok.sekar@broadcom.com>
[not found] ` <20160421092107.GA3673-418NljS/xK2EokMDITG9tw@public.gmane.org@broadcom.com>
2016-04-21 9:26 ` Mark Rutland
2016-04-19 18:54 ` [PATCH v5 4/7] arm64/perf: Define complete ARMv8 recommended implementation defined events Ashok Kumar
[not found] ` <1461092062-7484-5-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-20 14:24 ` Mark Rutland
2016-04-19 18:54 ` [PATCH v5 5/7] arm64/perf: Access pmu register using <read/write>_sys_reg Ashok Kumar
[not found] ` <1461092062-7484-6-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-20 11:12 ` Mark Rutland
2016-04-19 18:54 ` [PATCH v5 6/7] arm64/perf: Filter common events based on PMCEIDn_EL0 Ashok Kumar
[not found] ` <1461092062-7484-7-git-send-email-ashoks-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2016-04-20 14:52 ` Mark Rutland
2016-04-19 18:54 ` [PATCH v5 7/7] arm64/perf: Add Broadcom Vulcan PMU support Ashok Kumar
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=1461092062-7484-1-git-send-email-ashoks@broadcom.com \
--to=ashoks-dy08kvg/lbpwk0htik3j/w@public.gmane.org \
--cc=Suzuki.Poulose-5wv7dgnIgG8@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=jglauber-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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;
as well as URLs for NNTP newsgroup(s).