From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
ashoks@broadcom.com
Subject: [GIT PULL] arm64: perf updates for 4.7
Date: Mon, 16 May 2016 18:50:46 +0100 [thread overview]
Message-ID: <20160516175046.GB22358@arm.com> (raw)
Hi Linus,
Please pull the following arm64 perf updates for 4.7. The main addition
here is support for Broadcom's Vulcan core using the architected ID
registers for discovering supported events.
Cheers,
Will
--->8
The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb:
Linux 4.6-rc3 (2016-04-10 17:58:30 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-perf
for you to fetch changes up to 4ba2578fa7b557012b8f59ad7a9284ff15394338:
arm64: perf: don't expose CHAIN event in sysfs (2016-04-25 15:05:24 +0100)
----------------------------------------------------------------
arm64 perf updates for 4.7
- Support for the PMU in Broadcom's Vulcan CPU
- Dynamic event detection using the PMCEIDn_EL0 ID registers
----------------------------------------------------------------
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
Will Deacon (1):
arm64: perf: don't expose CHAIN event in sysfs
Documentation/devicetree/bindings/arm/pmu.txt | 3 +-
arch/arm64/boot/dts/broadcom/vulcan.dtsi | 2 +-
arch/arm64/kernel/perf_event.c | 553 +++++++++++++++++---------
include/linux/perf/arm_pmu.h | 2 +
4 files changed, 370 insertions(+), 190 deletions(-)
reply other threads:[~2016-05-16 17:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160516175046.GB22358@arm.com \
--to=will.deacon@arm.com \
--cc=ashoks@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=torvalds@linux-foundation.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