From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/7] arm: perf: factor arm_pmu core out to drivers
Date: Tue, 16 Jun 2015 17:17:28 +0100 [thread overview]
Message-ID: <20150616161728.GI30522@arm.com> (raw)
In-Reply-To: <1434041060-16378-2-git-send-email-mark.rutland@arm.com>
Hi Mark,
On Thu, Jun 11, 2015 at 05:44:14PM +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, with myself added as a reviewer as
> suggested by Will Deacon. The wildcard for arch/arm is updated to cover
> perf_regs.c and perf_callchain.c, which were added previously without a
> corresponding MAINTAINERS update.
>
> 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 ++++--
Can you put the MAINTAINERS changes in a separate patch, please?
> 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 ++--
I wonder whether that's such a good name for the subsystem. We already
have a bunch of perf_* headers directly under include/linux/ for the perf
core interfaces, so maybe drivers/pmu/ would be better?
Will
next prev parent reply other threads:[~2015-06-16 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 16:44 [PATCHv2 0/7] arm64: perf: heterogeneous PMU support Mark Rutland
2015-06-11 16:44 ` [PATCHv2 1/7] arm: perf: factor arm_pmu core out to drivers Mark Rutland
2015-06-16 16:17 ` Will Deacon [this message]
2015-06-16 21:44 ` Russell King - ARM Linux
2015-06-17 8:42 ` Will Deacon
2015-06-11 16:44 ` [PATCHv2 2/7] arm64: perf: factor out callchain code Mark Rutland
2015-06-11 16:44 ` [PATCHv2 3/7] arm64: perf: move to shared arm_pmu framework Mark Rutland
2015-06-11 16:44 ` [PATCHv2 4/7] arm64: perf: condense event number maps Mark Rutland
2015-06-11 16:44 ` [PATCHv2 5/7] arm64: perf: add Cortex-A53 support Mark Rutland
2015-06-11 16:44 ` [PATCHv2 6/7] arm64: perf: add Cortex-A57 support Mark Rutland
2015-06-11 16:44 ` [PATCHv2 7/7] arm64: dts: juno: describe PMUs separately Mark Rutland
2015-06-11 16:47 ` Liviu Dudau
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=20150616161728.GI30522@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 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).