linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jglauber@cavium.com (Jan Glauber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Cavium ThunderX PMU support
Date: Thu, 28 Jan 2016 15:54:58 +0100	[thread overview]
Message-ID: <cover.1453992560.git.jglauber@cavium.com> (raw)

Hi Mark & Will,

I'm resending the arm64 PMU patches. The only difference to the first
version is that I dropped the x on thunder in order to be consistent
with the existing device tree name.

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-28 14:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 14:54 Jan Glauber [this message]
2016-01-28 14:54 ` [PATCH v2 1/5] arm64/perf: Rename Cortex A57 events Jan Glauber
2016-01-28 14:55 ` [PATCH v2 2/5] arm64/perf: Add Cavium ThunderX PMU support Jan Glauber
2016-01-28 14:55 ` [PATCH v2 3/5] arm64: dts: Add Cavium ThunderX specific PMU Jan Glauber
2016-01-28 14:55 ` [PATCH v2 4/5] arm64/perf: Enable PMCR long cycle counter bit Jan Glauber
2016-01-28 14:55 ` [PATCH v2 5/5] arm64/perf: Extend event mask for ARMv8.1 Jan Glauber
2016-01-28 16:14   ` kbuild test robot
2016-01-28 17:33   ` kbuild test robot
2016-01-29  8:27     ` Jan Glauber
2016-01-29  8:29   ` Jan Glauber
2016-01-29 17:01     ` David Daney

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.1453992560.git.jglauber@cavium.com \
    --to=jglauber@cavium.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).