From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] Prepatory rework for multi-PMU support.
Date: Tue, 21 Oct 2014 14:11:16 +0100 [thread overview]
Message-ID: <1413897084-19715-1-git-send-email-mark.rutland@arm.com> (raw)
This series performs inital preparation for big.LITTLE perf support. It
depends on the CCI rework posted previously [1], as the removal of
get_hw_events and the percpu rework is incompatible with the single
global set of events the CCI has.
As a result of this series:
* The callchain handling is split from the PMU driver, as with metag,
powerpc, sh, and x86. This enables callchain handling for software
events when the kernel is built without CONFIG_HW_PERF_EVENTS.
* Legacy MIDR-based PMU probing is factored into a table that a
subsequent series will split into separate drivers. On its own this
should not result in a behavioural change.
* The ARM PMU accounting structures are reorganised and absorbed by
struct arm_pmu, which will make possible the allocation and management
of multiple PMUs in a later patch series.
Thanks,
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-October/295509.html
Mark Rutland (8):
arm: perf: factor out callchain code
arm: perf: make PMU probing data-driven
arm: perf: use IDR types for CPU PMUs
arm: perf: limit size of accounting data
arm: perf: kill get_hw_events()
arm: perf: fold percpu_pmu into pmu_hw_events
arm: perf: dynamically allocate cpu hardware data
arm: perf: fold hotplug notifer into arm_pmu
arch/arm/include/asm/perf_event.h | 2 +-
arch/arm/include/asm/pmu.h | 36 +++++++-
arch/arm/kernel/Makefile | 2 +-
arch/arm/kernel/perf_callchain.c | 137 ++++++++++++++++++++++++++++++
arch/arm/kernel/perf_event.c | 162 +++++-------------------------------
arch/arm/kernel/perf_event_cpu.c | 162 ++++++++++++++++--------------------
arch/arm/kernel/perf_event_v6.c | 12 +--
arch/arm/kernel/perf_event_v7.c | 14 ++--
arch/arm/kernel/perf_event_xscale.c | 20 ++---
9 files changed, 288 insertions(+), 259 deletions(-)
create mode 100644 arch/arm/kernel/perf_callchain.c
--
1.9.1
next reply other threads:[~2014-10-21 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 13:11 Mark Rutland [this message]
2014-10-21 13:11 ` [PATCH 1/8] arm: perf: factor out callchain code Mark Rutland
2014-10-21 13:11 ` [PATCH 2/8] arm: perf: make PMU probing data-driven Mark Rutland
2014-10-21 21:25 ` Stephen Boyd
2014-10-22 9:50 ` Mark Rutland
2014-10-21 13:11 ` [PATCH 3/8] arm: perf: use IDR types for CPU PMUs Mark Rutland
2014-10-21 21:25 ` Stephen Boyd
2014-10-22 10:06 ` Mark Rutland
2014-10-27 20:29 ` Stephen Boyd
2014-10-21 13:11 ` [PATCH 4/8] arm: perf: limit size of accounting data Mark Rutland
2014-10-21 13:11 ` [PATCH 5/8] arm: perf: kill get_hw_events() Mark Rutland
2014-10-21 13:11 ` [PATCH 6/8] arm: perf: fold percpu_pmu into pmu_hw_events Mark Rutland
2014-10-21 22:05 ` Stephen Boyd
2014-10-22 10:10 ` Mark Rutland
2014-10-21 13:11 ` [PATCH 7/8] arm: perf: dynamically allocate cpu hardware data Mark Rutland
2014-10-21 21:24 ` Stephen Boyd
2014-10-22 11:06 ` Mark Rutland
2014-10-21 13:11 ` [PATCH 8/8] arm: perf: fold hotplug notifier into arm_pmu Mark Rutland
2014-10-21 22:18 ` Stephen Boyd
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=1413897084-19715-1-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@arm.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).