From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: perf: split up perf_event.c by architecture
Date: Mon, 22 Nov 2010 16:38:20 -0000 [thread overview]
Message-ID: <000a01cb8a63$ac5c8110$05158330$@deacon@arm.com> (raw)
Hello,
This is version 2 of the patches originally posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2010-November/031503.html
The only patch that has changed is 5/5 which addresses some style comments
raised by Jean. Since the patch is over 100k, I've put it in my git repository
rather than posting it to the list (where it would be held for moderation).
Feedback welcome.
The following changes since commit 3561d43fd289f590fdae672e5eb831b8d5cf0bf6:
Linus Torvalds (1):
Linux 2.6.37-rc3
are available in the git repository at:
git://linux-arm.org/linux-2.6-wd.git perf-split
Will Deacon (5):
ARM: perf: consolidate common PMU behaviour
ARM: perf: avoid exposing internal stop function for v6 PMU
ARM: perf: add _init() functions to PMUs
ARM: perf: encode PMU name in arm_pmu structure
ARM: perf: separate PMU backends into multiple files
arch/arm/kernel/perf_event.c | 2448 +----------------------------------
arch/arm/kernel/perf_event_v6.c | 672 ++++++++++
arch/arm/kernel/perf_event_v7.c | 906 +++++++++++++
arch/arm/kernel/perf_event_xscale.c | 807 ++++++++++++
4 files changed, 2419 insertions(+), 2414 deletions(-)
create mode 100644 arch/arm/kernel/perf_event_v6.c
create mode 100644 arch/arm/kernel/perf_event_v7.c
create mode 100644 arch/arm/kernel/perf_event_xscale.c
next reply other threads:[~2010-11-22 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 16:38 Will Deacon [this message]
[not found] <-6296264039105571970@unknownmsgid>
2010-11-23 14:26 ` [PATCH v2] ARM: perf: split up perf_event.c by architecture Jean Pihet
2010-11-23 14:38 ` Will Deacon
[not found] ` <8976531311637671749@unknownmsgid>
2010-11-23 15:05 ` Jean Pihet
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='000a01cb8a63$ac5c8110$05158330$@deacon@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).