From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 1/9] arm: perf: factor arm_pmu core out to drivers
Date: Mon, 20 Jul 2015 17:13:19 +0100 [thread overview]
Message-ID: <20150720161318.GK9908@arm.com> (raw)
In-Reply-To: <1436181842-19402-2-git-send-email-mark.rutland@arm.com>
Hi Mark,
On Mon, Jul 06, 2015 at 12:23:53PM +0100, Mark Rutland wrote:
> To enable sharing of the arm_pmu code with arm64, this patch factors it
> out to drivers/perf/. A new drivers/perf directory is added for
> performance monitor drivers to live under.
>
> MAINTAINERS is updated accordingly. Files added previously without a
> corresponsing MAINTAINERS update (perf_regs.c, perf_callchain.c, and
> perf_event.h) are also added.
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: Will Deacon <will.deacon@arm.com>
> ---
> MAINTAINERS | 6 ++++--
> arch/arm/Kconfig | 8 ++------
> arch/arm/kernel/Makefile | 3 +--
> arch/arm/kernel/perf_event_v6.c | 2 +-
> arch/arm/kernel/perf_event_v7.c | 2 +-
> arch/arm/kernel/perf_event_xscale.c | 2 +-
> arch/arm/mach-ux500/cpu-db8500.c | 2 +-
> drivers/Kconfig | 2 ++
> drivers/Makefile | 1 +
> drivers/perf/Kconfig | 14 ++++++++++++++
> drivers/perf/Makefile | 1 +
> arch/arm/kernel/perf_event.c => drivers/perf/arm_pmu.c | 2 +-
> arch/arm/include/asm/pmu.h => include/linux/perf/arm_pmu.h | 4 ++--
> 13 files changed, 32 insertions(+), 17 deletions(-)
> create mode 100644 drivers/perf/Kconfig
> create mode 100644 drivers/perf/Makefile
> rename arch/arm/kernel/perf_event.c => drivers/perf/arm_pmu.c (99%)
> rename arch/arm/include/asm/pmu.h => include/linux/perf/arm_pmu.h (98%)
I'd like to take this for 4.3 on top of my current queue of ARM perf
updates. I've put together a branch, but it's not clear which tree this
should go through.
Russell: would you be ok taking this via the ARM tree, or would you
prefer it if I sent this via arm-soc? Personally, I think it makes sense
to send it to you along with the usual updates, but I appreciate you
don't normally touch drivers/ directly like this.
Will
next prev parent reply other threads:[~2015-07-20 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 11:23 [PATCHv3 0/9] arm64: perf: heterogeneous PMU support Mark Rutland
2015-07-06 11:23 ` [PATCHv3 1/9] arm: perf: factor arm_pmu core out to drivers Mark Rutland
2015-07-20 16:13 ` Will Deacon [this message]
2015-07-06 11:23 ` [PATCHv3 2/9] arm64: perf: factor out callchain code Mark Rutland
2015-07-06 11:23 ` [PATCHv3 3/9] arm64: perf: move to shared arm_pmu framework Mark Rutland
2015-07-06 11:23 ` [PATCHv3 4/9] arm64: perf: condense event number maps Mark Rutland
2015-07-06 11:23 ` [PATCHv3 5/9] arm64: perf: add Cortex-A53 support Mark Rutland
2015-07-06 11:23 ` [PATCHv3 6/9] arm64: perf: add Cortex-A57 support Mark Rutland
2015-07-06 11:23 ` [PATCHv3 7/9] arm64: dts: juno: describe PMUs separately Mark Rutland
2015-07-06 11:24 ` [PATCHv3 8/9] MAINTAINERS: update ARM PMU profiling and debugging for arm64 Mark Rutland
2015-07-06 11:24 ` [PATCHv3 9/9] MAINTAINERS: add myself as arm perf reviewer 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=20150720161318.GK9908@arm.com \
--to=will.deacon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.