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: Wed, 17 Jun 2015 09:42:56 +0100 [thread overview]
Message-ID: <20150617084255.GA6303@arm.com> (raw)
In-Reply-To: <20150616214432.GV7557@n2100.arm.linux.org.uk>
On Tue, Jun 16, 2015 at 10:44:32PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 16, 2015 at 05:17:28PM +0100, Will Deacon wrote:
> > 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?
>
> I think drivers/perf/ is better than drivers/pmu/. PMU can mean many
> things - performance monitor unit, power management unit, ...
>
> There comes a point where the use of TLAs becomes excessive, confusing
> and annoying, and I think this is it.
Okey doke, if the perf core guys don't mind the slightly odd namespace
split of <include/linux/perf_*.h> for the core stuff and
<include/linux/perf/*.h> for the PMU drivers, then we can stick with
Mark's proposal.
Will
next prev parent reply other threads:[~2015-06-17 8:42 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
2015-06-16 21:44 ` Russell King - ARM Linux
2015-06-17 8:42 ` Will Deacon [this message]
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=20150617084255.GA6303@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.