linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ashoks@broadcom.com (Ashok Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/7] arm64: perf: Broadcom Vulcan PMU support
Date: Thu, 21 Apr 2016 05:58:38 -0700	[thread overview]
Message-ID: <1461243525-13603-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 v5 [5]:
 Incorporated the following review comments from Mark.
 * Folded armv8pmu_probe_num_events and armv8pmu_read_common_events_bitmap.
 * Changed format string in event number print from 0x%02llx to 0x%03llx
 * Added ARM ARM doc number in commit logs wherever referenced.
 * Fixed sysreg.h order in perf_event.c

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
[5] http://www.spinics.net/lists/arm-kernel/msg498411.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 the 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, 369 insertions(+), 188 deletions(-)

-- 
2.1.0

             reply	other threads:[~2016-04-21 12:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 12:58 Ashok Kumar [this message]
2016-04-21 12:58 ` [PATCH v6 1/7] Documentation: arm64: pmu: Add Broadcom Vulcan PMU binding Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 2/7] arm64: dts: Add Broadcom Vulcan PMU in dts Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 3/7] arm64/perf: Changed events naming as per the ARM ARM Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 4/7] arm64/perf: Define complete ARMv8 recommended implementation defined events Ashok Kumar
2016-04-21 12:58 ` [PATCH v6 5/7] arm64/perf: Access pmu register using <read/write>_sys_reg Ashok Kumar
2016-04-25 13:06   ` Will Deacon
2016-04-25 13:12     ` Will Deacon
2016-04-21 12:58 ` [PATCH v6 6/7] arm64/perf: Filter common events based on PMCEIDn_EL0 Ashok Kumar
2016-04-21 13:49   ` Mark Rutland
2016-04-21 12:58 ` [PATCH v6 7/7] arm64/perf: Add Broadcom Vulcan PMU support Ashok Kumar
2016-04-21 13:54   ` Mark Rutland
2016-04-22 11:19     ` Jayachandran C

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=1461243525-13603-1-git-send-email-ashoks@broadcom.com \
    --to=ashoks@broadcom.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 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).