From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv4 0/6] arm64: perf: heterogeneous PMU support
Date: Wed, 7 Oct 2015 14:19:30 +0100 [thread overview]
Message-ID: <20151007131930.GJ16065@arm.com> (raw)
In-Reply-To: <1443779708-26789-1-git-send-email-mark.rutland@arm.com>
On Fri, Oct 02, 2015 at 10:55:02AM +0100, Mark Rutland wrote:
> This patch series moves the arm64 code over to the librified perf code now used
> by 32-bit arm, in the process gaining support for heterogeneous PMUs. Tailored
> support is then added for Cortex-A53 and Cortex-A57 as used in Juno systems.
>
> With this series applied, perf can be used to monitor 64-bit systems with
> heterogeneous PMUs in an identical fashion to 32-bit systems, e.g.
For the series:
Acked-by: Will Deacon <will.deacon@arm•com>
There's a trailing whitespace error in the first patch, but Catalin can
probably fix that up.
Will
next prev parent reply other threads:[~2015-10-07 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 9:55 [PATCHv4 0/6] arm64: perf: heterogeneous PMU support Mark Rutland
2015-10-02 9:55 ` [PATCHv4 1/6] arm64: perf: move to shared arm_pmu framework Mark Rutland
2015-10-02 9:55 ` [PATCHv4 2/6] arm64: perf: add Cortex-A53 support Mark Rutland
2015-10-02 9:55 ` [PATCHv4 3/6] arm64: perf: add Cortex-A57 support Mark Rutland
2015-10-02 9:55 ` [PATCHv4 4/6] arm64: dts: juno: describe PMUs separately Mark Rutland
2015-10-08 16:25 ` Liviu Dudau
2015-10-02 9:55 ` [PATCHv4 5/6] MAINTAINERS: update ARM PMU profiling and debugging for arm64 Mark Rutland
2015-10-02 9:55 ` [PATCHv4 6/6] MAINTAINERS: add myself as arm perf reviewer Mark Rutland
2015-10-07 13:19 ` Will Deacon [this message]
2015-10-07 13:27 ` [PATCHv4 0/6] arm64: perf: heterogeneous PMU support Catalin Marinas
2015-10-07 13:35 ` Mark Rutland
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=20151007131930.GJ16065@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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