linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Glauber <jan.glauber@gmail.com>
To: Will Deacon <will.deacon@arm.com>, Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Jan Glauber <jglauber@cavium.com>
Subject: [RFC PATCH 0/5] Cavium ThunderX PMU support
Date: Thu, 14 Jan 2016 13:55:40 +0100	[thread overview]
Message-ID: <cover.1452766568.git.jglauber@cavium.com> (raw)

Hi Will & Mark,

please have a look at these patches for perf PMU support. The Cavium
PMU stuff should be pretty generic but the long cycle counter bit
will change all ARMv8 PMUs and needs careful review.

Thanks,
Jan

Jan Glauber (5):
  arm64/perf: Rename Cortex A57 events
  arm64/perf: Add Cavium ThunderX PMU support
  arm64: dts: Add Cavium ThunderX specific PMU
  arm64/perf: Enable PMCR long cycle counter bit
  arm64/perf: Extend event mask for ARMv8.1

 Documentation/devicetree/bindings/arm/pmu.txt |   1 +
 arch/arm64/boot/dts/cavium/thunder-88xx.dtsi  |   5 +
 arch/arm64/kernel/perf_event.c                | 145 ++++++++++++++++++++------
 drivers/perf/arm_pmu.c                        |   5 +-
 include/linux/perf/arm_pmu.h                  |   4 +-
 5 files changed, 125 insertions(+), 35 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-01-14 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 12:55 Jan Glauber [this message]
2016-01-14 12:55 ` [RFC PATCH 1/5] arm64/perf: Rename Cortex A57 events Jan Glauber
2016-01-14 12:55 ` [RFC PATCH 2/5] arm64/perf: Add Cavium ThunderX PMU support Jan Glauber
2016-01-14 12:55 ` [RFC PATCH 3/5] arm64: dts: Add Cavium ThunderX specific PMU Jan Glauber
2016-01-14 14:47   ` Mark Rutland
2016-01-14 16:06     ` Jan Glauber
2016-01-14 12:55 ` [RFC PATCH 4/5] arm64/perf: Enable PMCR long cycle counter bit Jan Glauber
2016-01-14 12:55 ` [RFC PATCH 5/5] arm64/perf: Extend event mask for ARMv8.1 Jan Glauber

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=cover.1452766568.git.jglauber@cavium.com \
    --to=jan.glauber@gmail.com \
    --cc=jglauber@cavium.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=will.deacon@arm.com \
    /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).